Loading...
Loading...
Found 2,901 Skills
Core rules for bkit plugin. PDCA methodology, level detection, agent auto-triggering, and code quality standards. These rules are automatically applied to ensure consistent AI-native development. Use proactively when user requests feature development, code changes, or implementation tasks. Triggers: bkit, PDCA, develop, implement, feature, bug, code, design, document, 개발, 기능, 버그, 코드, 설계, 문서, 開発, 機能, バグ, 开发, 功能, 代码, desarrollar, función, error, código, diseño, documento, développer, fonctionnalité, bogue, code, conception, document, entwickeln, Funktion, Fehler, Code, Design, Dokument, sviluppare, funzionalità, bug, codice, design, documento Do NOT use for: documentation-only tasks, research, or exploration without code changes.
Manage editorial workflows for newsrooms and publications. Use when tracking story assignments, managing deadlines, coordinating editorial calendars, or establishing handoff protocols between reporters and editors. Includes templates for assignment tracking, editorial calendars, and workflow documentation.
Orchestrate in-session Task tool teams for parallel work. Fan-out research, implementation, review, and documentation across subagents. Use when: parallel tasks, fan-out, subagent team, Task tool, in-session agents.
Systematic approach to implementing new features in the Rust memory system following project conventions. Use when adding new functionality with proper testing and documentation, maintaining code quality and test coverage.
Use mcp__mdsel__mdsel for .md files unless reading entire file or planning to edit. Triggers: markdown, .md, README, documentation, docs
Central authority for Claude Code status line configuration. Covers custom status line creation, /statusline command, status line settings (statusLine in settings.json), JSON input structure (model, workspace, cost, session info), status line scripts (Bash, Python, Node.js), terminal color codes, git-aware status lines, helper functions, and status line troubleshooting. Supports creating custom status lines, configuring status line behavior, and displaying contextual session information. Delegates 100% to docs-management skill for official documentation.
Scrape documentation websites into local markdown files for AI context. Takes a base URL and crawls the documentation, storing results in ./docs (or custom path). Uses crawl4ai with BFS deep crawling.
Use this skill whenever Claude needs to fetch, read, extract, or analyze content from a web URL. Converts web pages into clean, token-efficient markdown using the markdown.new service instead of fetching raw HTML. Trigger when the user provides a URL and wants its content summarized, quoted, analyzed, compared, extracted, or processed. Also trigger when Claude needs to read documentation, blog posts, articles, wikis, release notes, changelogs, or any web-hosted text content. Even if the user just pastes a URL with no instruction, use this skill. Do NOT use for binary files, authenticated pages, or API endpoints returning JSON/XML.
Nx monorepo management skill for AI-native development. This skill should be used when working with Nx workspaces, project graphs, affected detection, code generation, and caching. Use when analyzing dependencies, running affected commands, generating code, configuring Nx Cloud, or optimizing build performance. Invoke nx-mcp tools for documentation queries.
Architecture analysis, violation detection, and pattern validation. USE WHEN: reviewing code architecture, identifying violations, verifying patterns, updating technical documentation. Reference: docs/02-architecture/ARCHITECTURE.md Examples: <example> Context: User wants to check if code follows architecture. user: "Analyze if the payment module follows our architecture" assistant: "I'll use architecture-analyzer to review against ARCHITECTURE.md." <commentary>Architectural review is architecture-analyzer specialty.</commentary> </example> <example> Context: Need to identify technical debt. user: "Find architectural violations in the services layer" assistant: "I'll use architecture-analyzer to scan for violations." <commentary>Violation detection is architecture-analyzer responsibility.</commentary> </example>
Orchestrates the release process - Testing, Documentation, and Tagging. Use when preparing a new version release.
When the user wants to design, optimize, or audit list layouts for content display. Also use when the user mentions "list layout," "list design," "vertical list," "stacked list," "blog list," "article list," "documentation list," "search results layout," or "infinite scroll list."