[email protected]

Plugin [email protected] from marketplace dotclaude in phantien133/dotclaude. Commands read from the repo's manifest — 1 month ago.

Skills (37)

• ai-regression-testing

  Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.

• api-design

  REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

• backend-patterns

  Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

• coding-standards

  Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

• continuous-learning-v2

  Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.

• database-migrations

  Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

• doc-coauthoring

  Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc

• f-extract

  Extract all Figma design data (nodes, components, tokens, assets) in one MCP round and write a persistent figma-snapshot.md. Run once per task — downstream steps read the snapshot, never call MCP again.

• f-implement

  Implement UI components and screens from a figma-snapshot.md file. Never calls Figma MCP. Never generates SVG or approximates icons. Tracks missing assets in figma-assets.md and gates on human export before completing.

• f-import
• f-page
• f-review
• f-ui-kit
• frontend-patterns

  Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

• github-ops

  GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task

• nestjs-patterns

  NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

• nextjs-turbopack

  Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

• postgres-patterns

  PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.

• security-review

  Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

• skill-creator

  Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better t

• dotclaude-component-picker

  Use when picking, vendoring, porting, or syncing agents, skills, commands, hooks, or rules from any upstream source (ECC = everything-claude-code, anthropic-skills, mcp-servers, wshobson/agents, or other external repos) into this dotclaude project's claudekit/ directory. Trigger on phrases like "pic

• tdd-workflow

  Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

• verification-loop

  A comprehensive verification system for Claude Code sessions.

• w-adr

  Phase 2 helper for w-task — append a new Architecture Decision Record entry to the project's ADR doc when impact analysis surfaces a new decision. Generic version of streaming-adr.

• w-api-doc

  Phase 5 helper for w-task — append/update module api.md with new API operations (GraphQL queries/mutations/subscriptions or REST endpoints) introduced or changed in the current task.

• w-checkpoint

  Create a standardized TDD checkpoint commit (RED or GREEN) during w-task Phase 4. Updates state.yaml with checkpoint timestamp.

• w-context-load

  Phase 0b helper for w-task — load module-aware context by reading module README + features/*.md + workflow-links, then write context.md. Generic version of dev-task's streaming-docs-aware context load.

• w-db-doc

  Phase 5 helper for w-task — write database/<NN>-<module>.md + sub-ERD .puml when DB changes occur. MANDATORY syncs the master ERD on every sub-ERD change — a stale master ERD is considered worse than none.

• w-doc-gate

  Phase 6 pre-PR gate — verify that every module touched in the current branch has a corresponding doc commit (module README / features / api.md / DB docs / master ERD). Blocks /w-pr if docs lag code. Replaces a post-merge sync hook by enforcing the invariant before PR creation.

• w-document-build-up

  Bootstrap streaming-docs-style documentation from an existing codebase. 4-phase state machine (Discover → Skeleton → ADR/OQ → Refinement) producing module READMEs, feature records, api.md, database schema docs, sub-ERDs, master ERD, ADR table, and OQ list. Run ONCE per project, BEFORE /w-setup, when

• w-feature-record

  Phase 5 helper for w-task — create or append features/<feature-name>.md inside the current module doc folder. Tracks per-feature history, design decisions, schema/API, diagrams, and constraints for future features.

• w-fix

  Lightweight workflow for bug fixes and small changes (1-3 files, <2h). Reads project config from .claude/workflow.yaml. Pass a GitHub issue URL, #N, or free description to start.

• w-impact-analyzer

  Phase 2 helper for w-task — auto-generate domain-specific impact.md sections (DB / GraphQL / queue / cache) by inspecting schema files referenced in workflow.yaml. Replaces hand-written generic Affected-Files-only impact.md with layer-aware analysis.

• w-oq-check

  Phase 0b helper for w-task — scan the project's Open Questions doc and surface OQs relevant to the current task. Flags blockers prominently. Generic version of streaming-oq-check.

• w-task

  Orchestrate a full feature dev workflow with browser verification (intake → context → plan → impact → UI → TDD → browser-verify → docs → PR). Adds Phase 4c localhost browser verification via Chrome DevTools MCP after TDD green. Reads project config from .claude/workflow.yaml.

• w-test-stubs

  Phase 4 helper for w-task — generate test file skeletons with layer-aware import boilerplate (unit / integration / graphql / bullmq / nestjs / nextjs) from impact.md, so TDD starts with structured RED, not blank files.

• workflow-setup

  One-time setup wizard that creates .claude/workflow.yaml — the project config consumed by dev-task, quick-fix, and all workflow skills. Run once per project before using any workflow skill.

Slash commands (8)

• /[email protected]:f-setup
• /[email protected]:feature-dev

  Guided feature development with codebase understanding and architecture focus

• /[email protected]:prp-plan

  Create comprehensive feature implementation plan with codebase analysis and pattern extraction

• /[email protected]:setup-dotclaude-preset-hooks

  Wire or unwire hooks for the installed dotclaude preset. Run when you want to enable or disable individual hooks in settings.json.

• /[email protected]:w-pr

  Create a GitLab merge request for the current branch using glab CLI. Reads MR settings from .claude/workflow.yaml. Pass a task slug to use plan.md as MR body, or provide a free description. Runs w-doc-gate first to enforce docs-with-code invariant.

• /[email protected]:w-reset

  Reset a w-task workflow back to phase 0, or wipe the task folder entirely. Reads state root from .claude/workflow.yaml.

• /[email protected]:w-setup

  One-time setup wizard that creates .claude/workflow.yaml — the project config consumed by w-task, w-fix, and all workflow skills. Spawns code-explorer to survey project structure before asking questions, so suggestions are accurate. Run once per project before using any workflow skill.

• /[email protected]:w-status

  Show the current w-task workflow state for one or all tasks without advancing it.

Subagents (7)

• code-architect

  Designs feature architectures by analyzing existing codebase patterns and conventions, then providing implementation blueprints with concrete files, interfaces, data flow, and build order.

• code-explorer

  Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, and documenting dependencies to inform new development.

• code-reviewer

  Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.

• code-simplifier

  Simplifies and refines code for clarity, consistency, and maintainability while preserving behavior. Focus on recently modified code unless instructed otherwise.

• planner

  Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.

• tdd-guide

  Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.

• typescript-reviewer

  Expert TypeScript/JavaScript code reviewer specializing in type safety, async correctness, Node/web security, and idiomatic patterns. Use for all TypeScript and JavaScript code changes. MUST BE USED for TypeScript/JavaScript projects.

Similar plugins