Docs-driven development skills: docs/ scaffolding, forward feature planning and citation-grounded reverse-engineering docs (both with lite/full output tiers and a doc-verifier subagent), a diagram-first DDD domain overview (context map) generator, a lightweight flow-diagram skill that diagrams a change just made, and opt-in translation mirror sync.
Plugin dev-docs from marketplace claude-skills in ywj3493/claude-skills. Commands read from the repo's manifest — 19 days ago.
dev-planningForward planning pipeline for a NEW feature or project (specification -> design documents -> test spec) with ID-based test traceability and lite/full output tiers (invoke as /dev-docs:dev-planning lite or full to pin the tier). Supports backend, frontend, and infrastructure domains. Do NOT use this
dev-reverse-docsReverse-engineer grounded planning/design/verification documentation from an EXISTING codebase, module, or feature, with mandatory per-claim source citation, a doc-verifier check after every pass, and lite/full output tiers (invoke as /dev-docs:dev-reverse-docs lite or full to pin the tier). Trigger
domain-overviewGenerate a diagram-first DDD domain overview document (docs/en/specifications/domain-overview.md) — one large Mermaid context map of bounded contexts and their aggregate roots, edges labeled with DDD context-map patterns (ACL, OHS, PL, SK, C/S, CF, Partnership) and upstream/downstream direction, plu
flow-diagramMake an implementation change explainable by writing or updating ONE Source-Linked sequence diagram for the flow that was just built or changed, merged into the domain's design/sequence-diagram.md. Triggers on "explain what you just built", "diagram this change", "시퀀스 다이어그램으로 설명해줘", "방금 작업 다이어그램으로 남
init-docsInitializes the standard docs/ directory structure for a new project. Asks for the source (base) language of the documentation (default en), records it in docs/config.yml, creates docs/<source>/{specifications,issue}/ plus docs/reference/, asks which working-rule files to install and seeds them into
sync-translationsAudits the source-language documentation directories (per docs/config.yml, default docs/en/) for documents that are missing a translation in a configured translation language (default docs/ko/), or where a translation appears out of date compared to its source, then creates or updates those translat
doc-verifierRead-only verifier that checks every [REF:]/[ASSUMED:] citation in a generated documentation file against the actual source code, and for sequence diagrams also cross-checks the visible Notes against the hidden CALLGRAPH block. Reports matched/mismatched/unsupported/excluded claim counts plus a mism
한국어 기획·개발설계·구현 플러그인. 새 프로젝트는 인프라·프로젝트 설정 → 요구사항 → 유저 스토리 → 정보 구조 → 유저 플로우 → 인터페이스 계약 순으로 기획하고 설계를 거쳐 4-Layered DDD 백엔드 코드까지 구현하며, 기존 코드베이스는 인프라 → 코드베이스 → 도메인별 설계를 먼저 뽑은 뒤 그 결과로부터 요구사항·유저 스토리·화면 구조를 역산한다. 백엔드는 4-Layered DDD, 프론트엔드는 FSD를 기준선으로 삼되 프레임워크에는 중립이며, 구현 단계의 언어별 관용구는 스택 프로파일로 분리한다. 인용 검증기와 목적별 탐색 서브에이전트(인프라·오퍼레이션·렌더링 흐름), 번역 미러 동기화를 포함한다. GitHub·Orca 없이 로컬 epic/leaf 이슈를 관리하고, 별도 스킬로 Orca 워크스페이스에 선택적으로 연결한다.
10 skills · 4 agents
한국어 GitHub 이슈 워크플로 플러그인. epic/leaf 계층(sub-issue), Draft PR로 시작, 선행 이슈와 Blocked, epic 체크리스트 동기화와 마무리, 수용 기준 개수 기반 규모 판정을 공통 규약 하나로 정하고, 이슈 번호로 Orca 워크스페이스를 이슈 계층과 같은 부모·자식 구조로 만든다.
3 skills
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
3 skills · 6 commands · 1 agent
Search and retrieve documents from local markdown files.
2 skills
PRD generation and conversion skills for the Ralph autonomous agent loop
2 skills
MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows
18 skills
Typeset professional documents and landing pages with the Kami design system.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.