Loading...
Loading...
Found 3,122 Skills
README construction — initialize template structure, generate per-package READMEs from doc comments, plan writing tasks, assemble root README from docs/ and package READMEs via doc.json config, and verify edits with `plan drift`.
Use when the user requests Chinese or Traditional Chinese output for responses, comments, docs, or localization, following Taiwan terminology (zh-Hant-TW/zh-TW/zh_TW).
Repository understanding and hierarchical codemap generation
Use when writing or editing files in src/content/blog/. Provides blog post structure and conventions.
Document project tools and CLI utilities in docs/define/tools/. Use when documenting internal CLIs, scripts, development tools, or third-party integrations that team members need to understand and use.
Top orchestrator for complete doc system. Delegates to ln-110 coordinator (project docs via 5 L3 workers) + ln-120-150 workers. Phase 4: global cleanup. Idempotent.
Use after brainstorming/design phase to create detailed implementation plans. Creates step-by-step plans clear enough for execution by any developer.
Comprehensive markdown linting guidance using markdownlint-cli2. Run, execute, check, and validate markdown files. Fix linting errors (MD0XX rules). Configure .markdownlint-cli2.jsonc (rules and ignores). Set up VS Code extension and GitHub Actions workflows. Supports markdown flavors including GitHub Flavored Markdown (GFM) and CommonMark. Use when working with markdown files, encountering validation errors, configuring markdownlint, setting up linting workflows, troubleshooting linting issues, establishing markdown quality standards, or configuring flavor-specific rules for tables, task lists, and strikethrough.
Use when writing or editing files in src/content/learn/. Provides Learn page structure and tone.
Reference page structure, templates, and writing patterns for src/content/reference/. For components, see /docs-components. For code examples, see /docs-sandpack.
Transforms technical documents into rigorous learning journeys with collegiate-level mastery requirements. Uses Bloom's taxonomy progression, 80%+ mastery thresholds, and multi-level verification before advancing. Treats learning as a high school to college graduation progression. Use when user wants deep understanding, not surface familiarity.
System architecture and technical design specialist. 🚨 TIER 2 SKILL - ON-DEMAND ACTIVATION 🚨 Use when user requests involve: - System architecture design and planning - Technical specifications and ADRs - Technology evaluation and selection - Scalability and performance planning - Integration architecture and API design - English: "design system", "architecture", "ADR", "tech stack", "scalability" - Swedish: "arkitektur", "systemdesign", "teknikval", "skalbarhet" Architecture Specialist (British female voice) provides: - System design and architecture patterns - Architecture Decision Records (ADRs) - Technology evaluation and trade-off analysis - Cloud and microservices architecture - Integration patterns and API design User confirmation optional but recommended for major architectural decisions.