Loading...
Loading...
Found 2,896 Skills
Configura proyectos con scripts de check y detecta CLIs. Usa cuando el usuario diga "configurar proyecto", "setup", "inicializar proyecto", "agregar npm run check", "qué CLIs tengo", o empiece a trabajar en un proyecto nuevo.
Create comprehensive steering documents for development projects. Generates project-specific standards, git workflows, and technology guidelines in .kiro/steering/ directory.
Guide for creating, refactoring, and optimizing AGENTS.md files (and CLAUDE.md files) for AI coding agent repositories. Use when the user wants to create a new AGENTS.md, refactor an existing one, audit their AGENTS.md for bloat or staleness, apply progressive disclosure principles, set up AGENTS.md in a monorepo, or improve how their AI coding agents behave via repository configuration files. Also applies to CLAUDE.md files (Claude Code's equivalent).
[Git & Release] Update CHANGELOG.md [Unreleased] section with business-focused entries via systematic file review
Create Architecture Decision Records (ADR) - Layer 5 artifact documenting architectural decisions with Context-Decision-Consequences format
Use when a Spec Kit feature has `spec.md` and you need a requirements-quality checklist (clarity, completeness, consistency, measurability, coverage), not implementation/runtime test cases.
Automatically check and update folder-specific AGENTS.md during research. Before investigating a domain, read nearest AGENTS.md for existing context. After discovering valuable patterns, append learnings to that file.
Complete Problem-Based Software Requirements Specification methodology following Gorski & Stadzisz research. Use when you need to perform requirements engineering from business problems to functional requirements with full traceability.
Translate "The Interactive Book of Prompting" chapters and UI strings to a new language
[Tooling & Meta] ClaudeKit usage guide - just type naturally
Use when creating Storybook stories, naming story exports, organizing story files, or reviewing story naming conventions. Ensures story names describe user scenarios and component states rather than implementation details.
Brief description of what this skill does and when to use it. Be specific about capabilities and use cases to help agents decide when to load this skill.