shinpr
UserDevelopment workflows for Claude Code that keep broad exploration focused on the outcome you approved.
Categories
Indexed Skills (57)
recipe-diagnose
Investigate problem, verify findings, and derive solutions
recipe-front-adjust
Adjust an already-implemented UI in-session with verification against the design source
recipe-front-build
Execute materialized frontend task files in autonomous execution mode
recipe-front-design
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval
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-task
Execute tasks following appropriate rules with rule-advisor metacognition
recipe-update-doc
Update existing design documents (Design Doc / PRD / ADR) with review
recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs
recipe-build
Execute materialized task files in autonomous execution mode
recipe-design
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
coding-principles
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
external-resource-context
Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions design source, design system, API schema, IaC source, secret store, or canonical source.
frontend-ai-guide
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
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.
documentation-criteria
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
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.
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
requirement-convergence
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.
subagents-orchestration-guide
Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
task-analyzer
Selects the smallest set of task-execution skills and metacognitive safeguards for standalone task and diagnosis workflows.
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.
test-implement
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
frontend-technical-spec
リポジトリの根拠に基づき、Reactの環境、コンポーネントアーキテクチャ、状態・データフロー、ビルド検証、フロントエンドの非機能基準を定義。Reactフロントエンド、そのビルド、ランタイム境界の設定・設計時に使用。
frontend-typescript-rules
React/TypeScriptの型安全性、コンポーネント設計、状態管理ルールを適用。Reactコンポーネント実装時に使用。
frontend-typescript-testing
リポジトリで設定済みのReactテスト・ブラウザハーネスを使用してフロントエンドテストを設計。RTL、MSW、Vitest、Playwrightが存在する場合に適用。コンポーネント、loading/error state、統合、フロントエンドE2Eテストの追加・レビュー時に使用。
typescript-testing
Vitestテスト設計と品質基準を適用。カバレッジ要件とモック使用ガイドを提供。ユニットテスト作成時に使用。
documentation-criteria
PRD、ADR、Design Doc、UI Spec、作業計画書の作成を支援。技術ドキュメントの作成・レビュー時、または「UI Spec/画面設計/コンポーネント分解」が言及された時に使用。
integration-e2e-testing
統合テストとE2Eテストを設計。モック境界と振る舞い検証ルールを適用。E2Eテスト、統合テスト作成時に使用。
llm-friendly-context
入力・出力・成功基準・決定事項・未解決条件を明確化し、下流エージェントが推測せず実行できるようにする。LLM向けのプロンプト・ハンドオフ・計画成果物・レビュー・レポート・生成指示を記述または改訂する時に使用。
requirement-convergence
変更が生むべき成果と、そこへ至るために提案された要件を切り分け、ユーザーが除外したものを記録し、コストを構造からバンドで見積もる。要件がワークフローに入った時点、設計を始める前、または「どこまでやるか/スコープ外は何か/やる価値があるか」が言及された時に使用。
subagents-orchestration-guide
規模に応じた計画、承認、実装、検証、エスカレーションのフローでサブエージェントを調整。サブエージェントへの作業振り分け、承認済み作業計画の実行、自律実行の再開時に使用。
task-analyzer
タスクの意図、変更リスク、実行規模を分類し、プロジェクトのスキルインデックスからスキルを選択。作業開始、タスクの振り分け、スコープ見積もり、スキル選択時に使用。
typescript-rules
型安全性とエラーハンドリングルールを適用。any禁止、型ガード必須。TypeScript実装、型定義レビュー時に使用。
image-generation
Optimizes image generation prompts using Subject-Context-Style structure. Use this skill when generating images, creating illustrations, photos, visual assets, editing images, or crafting prompts for any image generation model.
coding-standards
コードの品質問題、アンチパターン、可読性を検査。機能実装、コードレビュー、リファクタリング時に使用。
technical-spec
環境変数、アーキテクチャ設計、ビルド・テストコマンドを定義。環境設定、アーキテクチャ設計時に使用。
implementation-approach
実装戦略（垂直スライス、水平、ハイブリッド）をリスク評価で選択。機能の実装計画時に使用。
project-context
project-injectによってドメイン制約、フェーズ、規約、外部リソースへのアクセス方法がこのファイルに反映されるまで、プロジェクトコンテキストを未設定として示す。初回project-inject実行前にプロジェクトコンテキストを確認する場合に使用。
blueprint-standards
Defines structural design artifact formats — information architecture, user flows, content model, brand direction, and AI interaction model. Use when creating or reviewing structural design documents that precede prototype generation.
business-context
Provides Business Model Canvas, Value Proposition Canvas, and TAM/SAM/SOM market analysis frameworks. Use when assessing Viability risk, sizing markets, mapping value propositions, conducting competitive analysis, or identifying market gaps.
design-perspective
Integrates design principles, WCAG 2.2 AA accessibility, persona context, and state design into product decisions. Use when reviewing UX decisions, checking accessibility, applying design principles, or ensuring state coverage in acceptance criteria.
hypothesis-discipline
Manages hypothesis lifecycle, enforces validation criteria, time budgets, and confidence scoring rules. Use when creating hypotheses, updating confidence scores, setting validation criteria, handling timeouts, or recording validation results.
prd-standards
Defines PRD structure, user story format with 4 Risks assessment, EARS-format acceptance criteria, and delivery readiness thresholds. Use when writing PRDs, drafting user stories, defining acceptance criteria, or reviewing PRD quality and completeness.
product-principles
Defines 4 Risks confidence thresholds, OST hierarchy levels, Knowledge Pyramid tiers, and state design requirements. Use when evaluating user stories, setting confidence scores, referencing OST levels, scoping MVP, or determining validation sufficiency.
prototype-guide
Generates self-contained HTML prototypes with design context from project files. Read design principles, personas, and hypothesis files, then produce a working prototype for Usability and Value risk validation. Use when creating prototypes or validating through tangible artifacts.
recipe-blueprint
Define structural design foundation — information architecture, user flows, content model, brand direction, and AI interaction model — from validated opportunities and hypotheses
recipe-define
Orchestrate PRD creation from validated hypotheses — standard PRD output with 4 Risks confidence and hypothesis traceability
recipe-discover
Orchestrate Opportunity discovery and hypothesis generation through business and user perspectives
recipe-persona
Create or update personas with demographic, contextual, JTBD, and behavioral data
recipe-refine-visuals
Optional side-workflow for design experts to refine Concrete Tokens in brand-direction.md when a named downstream consumer needs reproducible values
recipe-reflect
Orchestrate structured reflection — update target artifacts with learnings, distill knowledge across hypotheses, and maintain INDEX.md
recipe-validate
Orchestrate hypothesis validation through type-appropriate methods — prototypes, code analysis, market research, and expert review
recipe-vision
Define or update product vision, strategy, outcomes, and NSM
galley
Authors and validates Galley task YAML, profiles, daemon handoff, run evidence, and queueing. Use when the user asks to create/repair/queue a Galley task, configure profiles/daemon/PR automation, or diagnose a Galley run.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.