Technical Writing

Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.

Use this when user needs to document business requirements from undocumented legacy code. Provides systematic 6-phase extraction: automated analysis, validation rules, use cases, business rules, data models, and workflow mapping. Apply for legacy system documentation, migration planning, compliance audits, or M&A due diligence

Use this skill when you need to write code for a page layout in the Next.js

Create detailed implementation plans with bite-sized tasks

Generate CLAUDE.md project memory files by exploring codebases. Use when user asks to "generate memory", "create CLAUDE.md", "document this project", "understand this codebase", or starts work on a new/unfamiliar repository. Triggers on new project onboarding and documentation requests.

Use when creating reusable process documentation. Apply TDD: baseline without skill → document failures → write skill → test → iterate. Four types: Discipline, Technique, Pattern, Reference. Iron Law: No skill without failing test first.

Create well-structured user stories with clear acceptance criteria in 'As a/I want/So that' format for team communication

Generate requirements-based test cases from Gherkin user stories using BDD methodology. Use this skill when the user asks to create test cases, generate test cases from user stories, analyze requirements for testing, convert user stories to test cases, or work with files in docs/user-stories/. This skill performs comprehensive requirement analysis and outputs Azure DevOps-compatible CSV test case files with proper formatting for import.

Look up GDScript and Godot Engine documentation using Deepwiki and Context7.Use when you need to find implementation approaches, APIs, or code examples for Godot projects.

Comprehensive assistance with godot_docs

Implement robust error handling with user-friendly messages, specific exception types, centralized handling, and graceful degradation. Use this skill when adding try-catch blocks, error boundaries, or exception handling. When creating custom error types or exception classes. When deciding where to handle errors (controller vs. service layer). When writing user-facing error messages. When implementing retry logic with exponential backoff. When ensuring resources are cleaned up in finally blocks or equivalent patterns.

Organize, create, and maintain documentation for projects. Use when the user asks to set up docs structure, write documentation, update existing docs, create READMEs, ADRs, guides, or any project documentation. Triggers include "organize my docs", "set up documentation", "write docs for this", "update the README", "document this", or when working on a project that needs documentation.

Provide lesson markdown templates for the AI-Native Robotics Textbook. Use when writing lessons, structuring educational content, or validating lesson format.

Creates assessments with varied question types (MCQ, code-completion, debugging, projects) alignedto learning objectives with meaningful distractors based on common misconceptions. Activate wheneducators design quizzes, exams, or tests measuring understanding; need questions at appropriatecognitive levels (Bloom's taxonomy); want balanced cognitive distribution (60%+ non-recall); orrequire rubrics for open-ended questions. Generates MCQs with diagnostic distractors, code-writingprompts, debugging challenges, and project-based assessments targeting deep understanding.

Guide technology selection workflow and ADR creation. Use when user asks about choosing a technology, comparing options, or needs to make a tech decision. Orchestrates discovery, evaluation, and documentation.

REST vs GraphQL, API versioning, rate limiting, and documentation for Elixir/BEAM APIs

정형화된 마크다운 문서 템플릿 사용 가이드

Write clean, consistent code following established naming conventions, automated formatting, DRY principles, meaningful variable names, small focused functions, and consistent indentation across all programming languages. Use this skill when writing or refactoring code in any programming language or file type including JavaScript (.js, .mjs, .cjs), TypeScript (.ts, .tsx, .mts), Python (.py), Ruby (.rb), Java (.java), Go (.go), Rust (.rs), PHP (.php), C# (.cs), Swift (.swift), Kotlin (.kt), or any other source code files. Use this when creating new functions, classes, interfaces, types, or variables that need appropriate naming following language-specific conventions like camelCase for JavaScript/TypeScript variables and functions (getUserById, totalPrice, isActive), PascalCase for class names, type names, and interfaces in most languages (UserProfile, DatabaseConnection, ApiResponse), snake_case for Python functions and variables (get_user_by_id, total_price, is_active), SCREAMING_SNAKE_CASE for constants (AP

Plan development sprints for Stapledons Voyage game features. Analyzes design docs, estimates effort considering AILANG constraints, and creates realistic sprint plans. Use when user asks to "plan sprint" or estimate game feature timelines.

Use semantic search to find relevant code and documentation when user asks about specific functionality, features, or implementation patterns. Automatically invoke when user asks "where is...", "how does... work", "find code that...", or similar conceptual queries. More powerful than grep for concept-based searches. Uses odino CLI with BGE embeddings for fully local semantic search.