jasonkneen/kiro
Overview
This skill generates comprehensive steering documents for development projects and places them under the .kiro/steering/ directory. It produces project-specific standards, git workflows, technology guidelines, and environment guidance tailored to the project type and scale. Outputs include front-matter to control inclusion logic so assistants include the right documents in context.
How this skill works
Analyze the project description, stack, and files to determine required documents and inclusion rules. Generate core templates such as project-standards.md and git-workflow.md, plus conditional files like frontend-standards.md or api-design.md based on file matches or manual inclusion. Emit files with clear front-matter and actionable content to enforce consistent coding, testing, security, and deployment practices.
When to use it
- Starting a new project and establishing standards and workflows
- Onboarding new team members who need concise project conventions
- Adding AI assistant guidance so code suggestions match your rules
- Preparing a repo for team reviews, CI, or open source publication
- Adapting standards when introducing new technologies or scale changes
Best practices
- Include minimal, specific front-matter: always, fileMatch, or manual
- Keep documents concise and example-driven to ensure actionability
- Use fileMatch patterns for language-specific guidance (package.json, *.tsx)
- Avoid duplication by centralizing cross-cutting rules in project-standards.md
- Update steering documents when architecture, security, or deployment changes
Example use cases
- React TypeScript e-commerce app: generate project-standards, git-workflow, frontend-standards, development-environment
- Python Django REST API: create project-standards, git-workflow, api-design, database-standards, env setup
- Microservices in Node.js: produce workflow, api-design (manual), service-level standards, deployment and monitoring guidance
- Component library: output documentation-standards, versioning-strategy, publishing-guidelines and git rules
FAQ
Files include front-matter with inclusion: fileMatch and fileMatchPattern so documents are pulled into context when matching repository files are present.
Can I customize templates for my team?
Yes. The templates are generated with clear sections to edit. Keep front-matter intact and adjust rules, examples, and tooling to match team preferences and scale.
6 skills
This skill generates comprehensive steering documents for a project, including standards, git workflows, and technology guidelines in .kiro/steering.
This skill converts approved requirements into detailed design documents outlining architecture, components, data models, and interfaces for implementation.
This skill converts designs into actionable, sequenced development tasks with clear objectives, dependencies, and measurable completion criteria.
This skill helps diagnose and resolve spec-driven development issues, guiding you through divergence, dependencies, unclear requirements, and execution
This skill converts vague feature ideas into clear, testable requirements using the EARS format, capturing user stories, criteria, and edge cases for
This skill guides spec-driven development by turning vague feature ideas into testable requirements, design documentation, and actionable tasks for reliable