[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AH0MJFCTCPRDQVT8BZYS0Y":3,"skill-same:01M7AH0MJFCTCPRDQVT8BZYS0Y":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7AH0MJFCTCPRDQVT8BZYS0Y","kiro-steering-custom",null,"Create custom steering documents for specialized project contexts","Huruikagi\u002Fspecbind","Huruikagi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10933612?v=4","01M7AGWP8QKD1EXMV26YA1ESXF","ふるいかぎ","01M7AGWP9WBJ1EEJNQKWB77GN3",2,"MIT","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-steering-custom\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kiro-steering-custom\ndescription: Create custom steering documents for specialized project contexts\nmetadata:\n  shared-rules: \"steering-principles.md\"\n---\n\n\n# Kiro Custom Steering Creation\n\n\u003Cbackground_information>\n**Role**: Create specialized steering documents beyond core files (product, tech, structure).\n\n**Mission**: Help users create domain-specific project memory for specialized areas.\n\n**Success Criteria**:\n- Custom steering captures specialized patterns\n- Follows same granularity principles as core steering\n- Provides clear value for specific domain\n\u003C\u002Fbackground_information>\n\n\u003Cinstructions>\n### Step 1: Gather Context\n\nIf steering context is already available from conversation, skip redundant file reads.\nOtherwise:\n- Check `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fsteering-custom\u002F` for available templates\n- Read `rules\u002Fsteering-principles.md` from this skill's directory for steering principles\n\n## Workflow\n\n1. **Ask user** for custom steering needs:\n   - Domain\u002Ftopic (e.g., \"API standards\", \"testing approach\")\n   - Specific requirements or patterns to document\n\n2. **Check if template exists**:\n   - Load from `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fsteering-custom\u002F{name}.md` if available\n   - Use as starting point, customize based on project\n\n3. **Analyze codebase** (JIT) for relevant patterns:\n\n#### Parallel Research\n\nThe following research areas are independent and can be executed in parallel:\n1. **Template & principles**: Load matching template and steering-principles.md\n2. **Domain patterns**: Analyze codebase for domain-specific patterns using Glob\u002FGrep\u002FRead\n\nIf multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.\n\nAfter all parallel research completes, synthesize findings for steering document.\n\n4. **Generate custom steering**:\n   - Follow template structure if available\n   - Apply principles from `rules\u002Fsteering-principles.md` from this skill's directory\n   - Focus on patterns, not exhaustive lists\n   - Keep to 100-200 lines (2-3 minute read)\n\n5. **Create file** in `{{KIRO_DIR}}\u002Fsteering\u002F{name}.md`\n\n## Available Templates\n\nTemplates available in `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fsteering-custom\u002F`:\n\n1. **api-standards.md** - REST\u002FGraphQL conventions, error handling\n2. **testing.md** - Test organization, mocking, coverage\n3. **security.md** - Auth patterns, input validation, secrets\n4. **database.md** - Schema design, migrations, query patterns\n5. **error-handling.md** - Error types, logging, retry strategies\n6. **authentication.md** - Auth flows, permissions, session management\n7. **deployment.md** - CI\u002FCD, environments, rollback procedures\n\nLoad template when needed, customize for project.\n\n## Steering Principles\n\nFrom `rules\u002Fsteering-principles.md` (in this skill's directory):\n\n- **Patterns over lists**: Document patterns, not every file\u002Fcomponent\n- **Single domain**: One topic per file\n- **Concrete examples**: Show patterns with code\n- **Maintainable size**: 100-200 lines typical\n- **Security first**: Never include secrets or sensitive data\n\n\u003C\u002Finstructions>\n\n## Tool guidance\n\n- **Read**: Load template, analyze existing code\n- **Glob**: Find related files for pattern analysis\n- **Grep**: Search for specific patterns\n- **Bash** with `ls`: Understand relevant structure\n\n**JIT Strategy**: Load template only when creating that type of steering.\n\n## Output description\n\nChat summary with file location (file created directly).\n\n```\n✅ Custom Steering Created\n\n## Created:\n- {{KIRO_DIR}}\u002Fsteering\u002Fapi-standards.md\n\n## Based On:\n- Template: api-standards.md\n- Analyzed: src\u002Fapi\u002F directory patterns\n- Extracted: REST conventions, error format\n\n## Content:\n- Endpoint naming patterns\n- Request\u002Fresponse format\n- Error handling conventions\n- Authentication approach\n\nReview and customize as needed.\n```\n\n## Examples\n\n### Success: API Standards\n**Input**: \"Create API standards steering\"  \n**Action**: Load template, analyze src\u002Fapi\u002F, extract patterns  \n**Output**: api-standards.md with project-specific REST conventions\n\n### Success: Testing Strategy\n**Input**: \"Document our testing approach\"  \n**Action**: Load template, analyze test files, extract patterns  \n**Output**: testing.md with test organization and mocking strategies\n\n## Safety & Fallback\n\n- **No template**: Generate from scratch based on domain knowledge\n- **Security**: Never include secrets (load principles)\n- **Validation**: Ensure doesn't duplicate core steering content\n\n## Notes\n\n- Templates are starting points, customize for project\n- Follow same granularity principles as core steering\n- All steering files loaded as project memory\n- Custom files equally important as core files\n- Avoid documenting agent-specific tooling directories (e.g. `.cursor\u002F`, `.gemini\u002F`, `.claude\u002F`)\n- Light references to `{{KIRO_DIR}}\u002Fspecs\u002F` and `{{KIRO_DIR}}\u002Fsteering\u002F` are acceptable; avoid other `.kiro\u002F` directories\n\n","# Kiro Custom Steering Creation\n\n\u003Cbackground_information>\n**Role**: Create specialized steering documents beyond core files (product, tech, structure).\n\n**Mission**: Help users create domain-specific project memory for specialized areas.\n\n**Success Criteria**:\n- Custom steering captures specialized patterns\n- Follows same granularity principles as core steering\n- Provides clear value for specific domain\n\u003C\u002Fbackground_information>\n\n\u003Cinstructions>\n### Step 1: Gather Context\n\nIf steering context is already available from conversation, skip redundant file reads.\nOtherwise:\n- Check `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fsteering-custom\u002F` for available templates\n- Read `rules\u002Fsteering-principles.md` from this skill's directory for steering principles\n\n## Workflow\n\n1. **Ask user** for custom steering needs:\n   - Domain\u002Ftopic (e.g., \"API standards\", \"testing approach\")\n   - Specific requirements or patterns to document\n\n2. **Check if template exists**:\n   - Load from `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fsteering-custom\u002F{name}.md` if available\n   - Use as starting point, customize based on project\n\n3. **Analyze codebase** (JIT) for relevant patterns:\n\n#### Parallel Research\n\nThe following research areas are independent and can be executed in parallel:\n1. **Template & principles**: Load matching template and steering-principles.md\n2. **Domain patterns**: Analyze codebase for domain-specific patterns using Glob\u002FGrep\u002FRead\n\nIf multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.\n\nAfter all parallel research completes, synthesize findings for steering document.\n\n4. **Generate custom steering**:\n   - Follow template structure if available\n   - Apply principles from `rules\u002Fsteering-principles.md` from this skill's directory\n   - Focus on patterns, not exhaustive lists\n   - Keep to 100-200 lines (2-3 minute read)\n\n5. **Create file** in `{{KIRO_DIR}}\u002Fsteering\u002F{name}.md`\n\n## Available Templates\n\nTemplates available in `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fsteering-custom\u002F`:\n\n1. **api-standards.md** - REST\u002FGraphQL conventions, error handling\n2. **testing.md** - Test organization, mocking, coverage\n3. **security.md** - Auth patterns, input validation, secrets\n4. **database.md** - Schema design, migrations, query patterns\n5. **error-handling.md** - Error types, logging, retry strategies\n6. **authentication.md** - Auth flows, permissions, session management\n7. **deployment.md** - CI\u002FCD, environments, rollback procedures\n\nLoad template when needed, customize for project.\n\n## Steering Principles\n\nFrom `rules\u002Fsteering-principles.md` (in this skill's directory):\n\n- **Patterns over lists**: Document patterns, not every file\u002Fcomponent\n- **Single domain**: One topic per file\n- **Concrete examples**: Show patterns with code\n- **Maintainable size**: 100-200 lines typical\n- **Security first**: Never include secrets or sensitive data\n\n\u003C\u002Finstructions>\n\n## Tool guidance\n\n- **Read**: Load template, analyze existing code\n- **Glob**: Find related files for pattern analysis\n- **Grep**: Search for specific patterns\n- **Bash** with `ls`: Understand relevant structure\n\n**JIT Strategy**: Load template only when creating that type of steering.\n\n## Output description\n\nChat summary with file location (file created directly).\n\n```\n✅ Custom Steering Created\n\n## Created:\n- {{KIRO_DIR}}\u002Fsteering\u002Fapi-standards.md\n\n## Based On:\n- Template: api-standards.md\n- Analyzed: src\u002Fapi\u002F directory patterns\n- Extracted: REST conventions, error format\n\n## Content:\n- Endpoint naming patterns\n- Request\u002Fresponse format\n- Error handling conventions\n- Authentication approach\n\nReview and customize as needed.\n```\n\n## Examples\n\n### Success: API Standards\n**Input**: \"Create API standards steering\"  \n**Action**: Load template, analyze src\u002Fapi\u002F, extract patterns  \n**Output**: api-standards.md with project-specific REST conventions\n\n### Success: Testing Strategy\n**Input**: \"Document our testing approach\"  \n**Action**: Load template, analyze test files, extract patterns  \n**Output**: testing.md with test organization and mocking strategies\n\n## Safety & Fallback\n\n- **No template**: Generate from scratch based on domain knowledge\n- **Security**: Never include secrets (load principles)\n- **Validation**: Ensure doesn't duplicate core steering content\n\n## Notes\n\n- Templates are starting points, customize for project\n- Follow same granularity principles as core steering\n- All steering files loaded as project memory\n- Custom files equally important as core files\n- Avoid documenting agent-specific tooling directories (e.g. `.cursor\u002F`, `.gemini\u002F`, `.claude\u002F`)\n- Light references to `{{KIRO_DIR}}\u002Fspecs\u002F` and `{{KIRO_DIR}}\u002Fsteering\u002F` are acceptable; avoid other `.kiro\u002F` directories\n\n",{"name":5,"metadata":24,"description":7},{"shared-rules":25},"steering-principles.md","main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-steering-custom",0,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind","https:\u002F\u002Fgithub.com\u002FHuruikagi","2026-11-04 13:59:47",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Huruikagi\u002Fspecbind --skill kiro-steering-custom",{"tool":39,"command":40},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill kiro-steering-custom",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill kiro-steering-custom","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-steering-custom\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",178,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-steering-custom\u002Fagents\u002Fopenai.yaml",[54,60,65,72,79,86],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7AH3VQ2VR2X159H99G73TGE","kiro-spec-init","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Ftests\u002Ffixtures\u002Fmigration\u002Fminimal\u002F.agents\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],{"skillNo":61,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7AH3RXXAHA50BR132P0M955","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Ftests\u002Ffixtures\u002Fmigration\u002Fguided\u002F.claude\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AH3KZBF4YBG4Q8628WD50S","sb-verify-completion","Consequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-verify-completion\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AH3EFD7KC9RGPZFZE0YNA6","sb-validate-implementation","Validate completed Tasks against active Requirement IDs and record completion on GO under an explicit lifecycle-validation request or ordinary Drive authority. Also owns completion withdrawal under an evidenced Drive replan recovery handoff. For a consequence-free claim check, use sb-verify-completion.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-validate-implementation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AH38XP0RT7N8G5M74N7FD5","sb-validate-design","Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-validate-design\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AH344YTCDM8E8FTSJHC8WF","sb-steering","Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-steering\u002FSKILL.md",[],[]]