Technical Writing

Comprehensive 9-step development workflow ensuring quality through planning, implementation, review, testing, and documentation with worktree isolation. Includes agent assignments, quality gates, and AskUserQuestion usage. Use when orchestrating feature development or understanding the development process.

Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

Enforces documentation standards and structure for this project. This skill should be used when creating, updating, or organizing documentation to ensure compliance with project rules, prevent redundancy, and maintain screen-based organization. Activates when user asks to create/update docs or when documentation needs to be generated.

Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.

This skill should be used when working with Supabase database operations in the MyJKKN project, including creating modules, updating schemas, writing RLS policies, creating database functions, implementing Auth SSR, or developing Edge Functions. Automatically triggers when user mentions 'database', 'table', 'SQL', 'Supabase', 'migration', 'RLS', 'policy', or 'Edge Function'.

Set up or fix Docker Compose, Nginx edge routing, healthchecks, and service wiring for WordPress headless (MariaDB), Astro, and Supabase self-hosted in C:\digitalbitsolutions\wordpress_headless. Use when asked to make docker compose up --build work, update edge routing, or adjust .env.example/README for this WP + Astro + Supabase stack.

Guide for writing clean, maintainable code following industry best practices and design principles like DRY, SOLID, and composition patterns. Use when writing any code to ensure consistency, readability, and long-term maintainability across all programming languages.

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Handle template comparison and optimization workflows including backup detection, smart merging, and update completion reporting. Enhanced with Context7 MCP for up-to-date documentation.

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

ライブラリやフレームワークのドキュメントが必要な場合に自動発動。Context7 MCPを使用して最新の公式ドキュメントを取得する。

Trove is a minimal logging facade for Clojure/Script supporting both traditional and structured logging. Use when writing libraries that need logging without forcing a backend choice, or when you need rich data-oriented logging with flexible filtering.

Prevent SQL injection by using $queryRaw tagged templates instead of $queryRawUnsafe. Use when writing raw SQL queries or dynamic queries.

Logs architectural decisions to docs/DECISIONS.md in ADR format.Use when: making significant architectural or technology choices.Integrates with /craft and /why commands.

Auto-check and update key documentation before Git commits to keep docs in sync with code.LOAD THIS SKILL WHEN: Before git commit/push | User says "準備提交", "sync docs", "發布", "release" | code changes affect documentation.CAPABILITIES: Update README, CHANGELOG, ROADMAP, ARCHITECTURE, Memory Bank; minimal changes; semantic versioning; Keep a Changelog format.

Write comments explaining WHAT and WHY, never temporal context or history

Lightweight search utility for Toss / Apps-in-Toss llms-full.txt docs, caching sources and ranking snippets with keyword + similarity (Korean-aware) scoring.

Use ONLY when the user explicitly says: 'use the skill web-to-markdown ...' (or 'use a skill web-to-markdown ...'). Converts webpage URLs to clean Markdown by calling the local web2md CLI (Puppeteer + Readability), suitable for JS-rendered pages.

Review workscript node implementations for alignment with NODE_DEVELOPMENT_BLUEPRINT.md and consistency with the new-node skill. Use when reviewing node code, auditing node implementations, checking for compliance with single-edge return pattern, validating ai_hints metadata consistency, or ensuring thorough documentation of state interactions. Triggers on requests like "review this node", "check node compliance", "audit node implementation", or "validate node metadata".