typescript7-lsp
claudeTypeScript 7's native language server (tsc --lsp --stdio) from the project's own TypeScript. Replaces typescript-lsp, which needs the tsserver TypeScript 7 no longer ships.
Claude Code and Codex plugins their authors filed under "development". All categories.
TypeScript 7's native language server (tsc --lsp --stdio) from the project's own TypeScript. Replaces typescript-lsp, which needs the tsserver TypeScript 7 no longer ships.
Go language server for code intelligence and refactoring. Vendored from anthropics/claude-plugins-official and pinned for review.
Skills for working in the React core monorepo: extracting error codes, managing feature flags, running Flow type-checks, formatting/linting, and running tests across release channels.
Code review, refactoring, and Jira/GitHub workflows.
Semantic memory system for Claude Code with persistent context retention through vector embeddings
Essential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design
Language-specific expert agents with deep framework knowledge - Python, TypeScript, Go, Rust, Java, and more
Essential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design
Language-specific expert agents with deep framework knowledge - Python, TypeScript, Go, Rust, Java, and more
Orchestrates complete feature development using specialized agents. Discovery, exploration, architecture, implementation, review, and retrospective phases.
Fortran language server (fortls) for code intelligence — go-to-definition, find-references, symbol search, hover, and diagnostics across free-form and fixed-form Fortran. Wires fortls into Claude Code's built-in LSP tool. Requires `fortls` on PATH (pip install fortls).
Complete sprint lifecycle with planning, implementation, quality gates, code review, and retrospective. Coordinates dev-plan-architect, code critics, and retrospective analysts.
Control the user's real Google Chrome (their profile, cookies and logged-in sessions) from the terminal via the Chrome DevTools Protocol: navigate, capture (incl. full page and per breakpoint), read console/DOM, fill forms, export to PDF, annotate elements, and group tabs. No extension, no MCP, no npm dependencies.
Logic Gate + Iron Rule: triage what actually needs tests, then strict test-first development for anything with logic. Ported from ravila4/claude-adhd-skills.
Essential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design
Language-specific expert agents with deep framework knowledge - Python, TypeScript, Go, Rust, Java, and more
GitHub from the shell: issues, pull requests, stacked PRs, workflow runs, releases, Projects, Actions secrets, gists, and raw API access.
Drive a real Chrome session: navigate, click, fill forms, run JavaScript, read console and network, screenshot, audit performance.
Essential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design
Language-specific expert agents with deep framework knowledge - Python, TypeScript, Go, Rust, Java, and more
Complete product-development agent team — 72 specialists across the full lifecycle from discovery to ship. Includes agent-dispatcher + /dispatch slash command. Companion: marketing-pack.
Essential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design
Language-specific expert agents with deep framework knowledge - Python, TypeScript, Go, Rust, Java, and more
Debugging tools (skill-graph, explain-ranking, workflow-debug, command-validate)
YAML language server for Claude Code, powered by yaml-language-server: schema-aware diagnostics, completions, hover, and validation for .yaml and .yml files.
Install and configure @jimdrury/storyblok-component-schema in a project. Registry setup, config file, credentials, and CI integration.
Create and configure Storyblok component definitions using the TypeScript schema DSL. Component types, field types, tabs, block restrictions, and validation.
Use the contentType() factory to define root-level Storyblok components like pages, articles, or settings.
Reference for Neovim's Lua API surface (vim.api, vim.fn, and builtin helpers such as vim.schedule, vim.wait, vim.ui_*). Use when writing or editing Neovim Lua plugins/configs, or when an agent needs exact vim.api/vim.fn signatures.
Reference for vim.diagnostic and diagnostic-namespace APIs in Neovim Lua (signs, virtual text/lines, goto next/prev, qf/loclist, enable/disable). Use when implementing diagnostics display or navigation.