shinpr.

frontend-technical-spec

Defines React environment, component architecture, state/data flow, build verification, and frontend non-functional criteria from repository evidence. Use when configuring or designing a React frontend, its build, or its runtime boundaries.

frontend-typescript-rules

Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.

frontend-typescript-testing

Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest, and Playwright when present. Use when adding or reviewing component, loading/error-state, integration, or frontend E2E tests.

llm-friendly-context

Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream agents can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.

project-context

Marks project context as unconfigured until project-inject materializes domain constraints, phase, conventions, and external-resource access in this file. Use when checking project context before the initial project-inject run.

skill-optimization

Evaluates and optimizes skill file quality using 8 content patterns and 9 editing principles. Use when creating skills, refining skill content, or auditing skill quality.

technical-spec

Defines environment variables, architecture design, and build/test commands. Use when configuring environment or designing architecture.

ai-development-guide

Technical decision criteria, anti-pattern detection, debugging techniques, and quality check workflow. Use when making technical decisions, detecting code smells, or performing quality assurance.

coding-principles

Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.

documentation-criteria

Documentation creation criteria including PRD, ADR, Design Doc, and Work Plan requirements with templates. Use when creating or reviewing technical documents, or determining which documents are required.

frontend-ai-guide

Frontend-specific technical decision criteria, anti-patterns, debugging techniques, and quality check workflow. Use when making frontend technical decisions or performing quality assurance.

implementation-approach

Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.

integration-e2e-testing

Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.

recipe-add-integration-tests

Add integration/E2E tests to existing codebase using Design Docs

recipe-build

Execute decomposed tasks in autonomous execution mode

recipe-design

Execute from requirement analysis to design document creation

recipe-diagnose

Investigate problem, verify findings, and derive solutions

recipe-front-build

Execute frontend implementation in autonomous execution mode

recipe-front-design

Execute from requirement analysis to frontend design document creation

recipe-front-plan

Create frontend work plan from design document and obtain plan approval

recipe-front-review

Design Doc compliance and security validation with optional auto-fixes

recipe-fullstack-build

Execute decomposed fullstack tasks with layer-aware agent routing

recipe-fullstack-implement

Orchestrate full-cycle implementation across backend and frontend layers

recipe-implement

Orchestrate the complete implementation lifecycle from requirements to deployment

recipe-plan

Create work plan from design document and obtain plan approval

recipe-reverse-engineer

Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow

recipe-review

Design Doc compliance and security validation with optional auto-fixes

recipe-task

Execute tasks following appropriate rules with rule-advisor metacognition

recipe-update-doc

Update existing design documents (Design Doc / PRD / ADR) with review

subagents-orchestration-guide

Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.

task-analyzer

Performs metacognitive task analysis and skill selection. Use when determining task complexity, selecting appropriate skills, or estimating work scale.

test-implement

Test implementation patterns and conventions. Use when implementing unit tests, integration tests, or E2E tests, including RTL+Vitest+MSW component testing and Playwright E2E testing.

testing-principles

Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.

typescript-rules

React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.

mcp-local-rag

Search, ingest, expand chunk context, or manage local documents via a local RAG MCP server (tools: query_documents, read_chunk_neighbors, ingest_file, ingest_data, delete_file, list_files). Use when user says "search my docs", "save this page", "read around that chunk", "what did I save about X", or invokes `npx mcp-local-rag`.

sub-agents

Run agent definitions as sub-agents. Use when the user names an agent or sub-agent to run, references an agent definition, or delegates a task to an agent.