kiro-steering-custom

Name: kiro-steering-custom
Author: gotalab

3.6kstars271forks

How to install kiro-steering-custom?

gotalab/cc-sdd/kiro-steering-custom

$npx -y skills add gotalab/cc-sdd --skill kiro-steering-custom

Installs into the current project.

Summary

Create custom steering documents for specialized project contexts

Files · 1

View on GitHub

SKILL.md

1	# Kiro Custom Steering Creation
2
3	<background_information>
4	Role: Create specialized steering documents beyond core files (product, tech, structure).
5
6	Mission: Help users create domain-specific project memory for specialized areas.
7
8	Success Criteria:
9	- Custom steering captures specialized patterns
10	- Follows same granularity principles as core steering
11	- Provides clear value for specific domain
12	</background_information>
13
14	<instructions>
15	### Step 1: Gather Context
16
17	If steering context is already available from conversation, skip redundant file reads.
18	Otherwise:
19	- Check `{{KIRO_DIR}}/settings/templates/steering-custom/` for available templates
20	- Read `rules/steering-principles.md` from this skill's directory for steering principles
21
22	## Workflow
23
24	1. Ask user for custom steering needs:
25	- Domain/topic (e.g., "API standards", "testing approach")
26	- Specific requirements or patterns to document
27
28	2. Check if template exists:
29	- Load from `{{KIRO_DIR}}/settings/templates/steering-custom/{name}.md` if available
30	- Use as starting point, customize based on project
31
32	3. Analyze codebase (JIT) for relevant patterns:
33
34	#### Parallel Research
35
36	The following research areas are independent and can be executed in parallel:
37	1. Template & principles: Load matching template and steering-principles.md
38	2. Domain patterns: Analyze codebase for domain-specific patterns using Glob/Grep/Read
39
40	If multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.
41
42	After all parallel research completes, synthesize findings for steering document.
43
44	4. Generate custom steering:
45	- Follow template structure if available
46	- Apply principles from `rules/steering-principles.md` from this skill's directory
47	- Focus on patterns, not exhaustive lists
48	- Keep to 100-200 lines (2-3 minute read)
49
50	5. Create file in `{{KIRO_DIR}}/steering/{name}.md`
51
52	## Available Templates
53
54	Templates available in `{{KIRO_DIR}}/settings/templates/steering-custom/`:
55
56	1. api-standards.md - REST/GraphQL conventions, error handling
57	2. testing.md - Test organization, mocking, coverage
58	3. security.md - Auth patterns, input validation, secrets
59	4. database.md - Schema design, migrations, query patterns
60	5. error-handling.md - Error types, logging, retry strategies
61	6. authentication.md - Auth flows, permissions, session management
62	7. deployment.md - CI/CD, environments, rollback procedures
63
64	Load template when needed, customize for project.
65
66	## Steering Principles
67
68	From `rules/steering-principles.md` (in this skill's directory):
69
70	- Patterns over lists: Document patterns, not every file/component
71	- Single domain: One topic per file
72	- Concrete examples: Show patterns with code
73	- Maintainable size: 100-200 lines typical
74	- Security first: Never include secrets or sensitive data
75
76	</instructions>
77
78	## Tool guidance
79
80	- Read: Load template, analyze existing code
81	- Glob: Find related files for pattern analysis
82	- Grep: Search for specific patterns
83	- Bash with `ls`: Understand relevant structure
84
85	JIT Strategy: Load template only when creating that type of steering.
86
87	## Output description
88
89	Chat summary with file location (file created directly).
90
91	```
92	✅ Custom Steering Created
93
94	## Created:
95	- {{KIRO_DIR}}/steering/api-standards.md
96
97	## Based On:
98	- Template: api-standards.md
99	- Analyzed: src/api/ directory patterns
100	- Extracted: REST conventions, error format
101
102	## Content:
103	- Endpoint naming patterns
104	- Request/response format
105	- Error handling conventions
106	- Authentication approach
107
108	Review and customize as needed.
109	```
110
111	## Examples
112
113	### Success: API Standards
114	Input: "Create API standards steering"
115	Action: Load template, analyze src/api/, extract patterns
116	Output: api-standards.md with project-specific REST conventions
117
118	### Success: Testing Strategy
119	Input: "Document our testing approach"
120	Action: Load template, analyze test files, extract patterns
121	Output: testing.md with test organization and mocking strategies
122
123	## Safety & Fallback
124
125	- No template: Generate from scratch based on domain knowledge
126	- Security: Never include secrets (load principles)
127	- Validation: Ensure doesn't duplicate core steering content
128
129	## Notes
130
131	- Templates are starting points, customize for project
132	- Follow same granularity principles as core steering
133	- All steering files loaded as project memory
134	- Custom files equally important as core files
135	- Avoid documenting agent-specific tooling directories (e.g. `.cursor/`, `.gemini/`, `.claude/`)
136	- Light references to `{{KIRO_DIR}}/specs/` and `{{KIRO_DIR}}/steering/` are acceptable; avoid other `.kiro/` directories

People who liked this also viewed

6 picks

Type

kiro-steering-custom

3.6kstars271forks

View on GitHub

How to install kiro-steering-custom?

gotalab/cc-sdd/kiro-steering-custom

$npx -y skills add gotalab/cc-sdd --skill kiro-steering-custom

Installs into the current project.

Summary

Create custom steering documents for specialized project contexts

Files · 1

View on GitHub

SKILL.md

1	# Kiro Custom Steering Creation
2
3	<background_information>
4	Role: Create specialized steering documents beyond core files (product, tech, structure).
5
6	Mission: Help users create domain-specific project memory for specialized areas.
7
8	Success Criteria:
9	- Custom steering captures specialized patterns
10	- Follows same granularity principles as core steering
11	- Provides clear value for specific domain
12	</background_information>
13
14	<instructions>
15	### Step 1: Gather Context
16
17	If steering context is already available from conversation, skip redundant file reads.
18	Otherwise:
19	- Check `{{KIRO_DIR}}/settings/templates/steering-custom/` for available templates
20	- Read `rules/steering-principles.md` from this skill's directory for steering principles
21
22	## Workflow
23
24	1. Ask user for custom steering needs:
25	- Domain/topic (e.g., "API standards", "testing approach")
26	- Specific requirements or patterns to document
27
28	2. Check if template exists:
29	- Load from `{{KIRO_DIR}}/settings/templates/steering-custom/{name}.md` if available
30	- Use as starting point, customize based on project
31
32	3. Analyze codebase (JIT) for relevant patterns:
33
34	#### Parallel Research
35
36	The following research areas are independent and can be executed in parallel:
37	1. Template & principles: Load matching template and steering-principles.md
38	2. Domain patterns: Analyze codebase for domain-specific patterns using Glob/Grep/Read
39
40	If multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.
41
42	After all parallel research completes, synthesize findings for steering document.
43
44	4. Generate custom steering:
45	- Follow template structure if available
46	- Apply principles from `rules/steering-principles.md` from this skill's directory
47	- Focus on patterns, not exhaustive lists
48	- Keep to 100-200 lines (2-3 minute read)
49
50	5. Create file in `{{KIRO_DIR}}/steering/{name}.md`
51
52	## Available Templates
53
54	Templates available in `{{KIRO_DIR}}/settings/templates/steering-custom/`:
55
56	1. api-standards.md - REST/GraphQL conventions, error handling
57	2. testing.md - Test organization, mocking, coverage
58	3. security.md - Auth patterns, input validation, secrets
59	4. database.md - Schema design, migrations, query patterns
60	5. error-handling.md - Error types, logging, retry strategies
61	6. authentication.md - Auth flows, permissions, session management
62	7. deployment.md - CI/CD, environments, rollback procedures
63
64	Load template when needed, customize for project.
65
66	## Steering Principles
67
68	From `rules/steering-principles.md` (in this skill's directory):
69
70	- Patterns over lists: Document patterns, not every file/component
71	- Single domain: One topic per file
72	- Concrete examples: Show patterns with code
73	- Maintainable size: 100-200 lines typical
74	- Security first: Never include secrets or sensitive data
75
76	</instructions>
77
78	## Tool guidance
79
80	- Read: Load template, analyze existing code
81	- Glob: Find related files for pattern analysis
82	- Grep: Search for specific patterns
83	- Bash with `ls`: Understand relevant structure
84
85	JIT Strategy: Load template only when creating that type of steering.
86
87	## Output description
88
89	Chat summary with file location (file created directly).
90
91	```
92	✅ Custom Steering Created
93
94	## Created:
95	- {{KIRO_DIR}}/steering/api-standards.md
96
97	## Based On:
98	- Template: api-standards.md
99	- Analyzed: src/api/ directory patterns
100	- Extracted: REST conventions, error format
101
102	## Content:
103	- Endpoint naming patterns
104	- Request/response format
105	- Error handling conventions
106	- Authentication approach
107
108	Review and customize as needed.
109	```
110
111	## Examples
112
113	### Success: API Standards
114	Input: "Create API standards steering"
115	Action: Load template, analyze src/api/, extract patterns
116	Output: api-standards.md with project-specific REST conventions
117
118	### Success: Testing Strategy
119	Input: "Document our testing approach"
120	Action: Load template, analyze test files, extract patterns
121	Output: testing.md with test organization and mocking strategies
122
123	## Safety & Fallback
124
125	- No template: Generate from scratch based on domain knowledge
126	- Security: Never include secrets (load principles)
127	- Validation: Ensure doesn't duplicate core steering content
128
129	## Notes
130
131	- Templates are starting points, customize for project
132	- Follow same granularity principles as core steering
133	- All steering files loaded as project memory
134	- Custom files equally important as core files
135	- Avoid documenting agent-specific tooling directories (e.g. `.cursor/`, `.gemini/`, `.claude/`)
136	- Light references to `{{KIRO_DIR}}/specs/` and `{{KIRO_DIR}}/steering/` are acceptable; avoid other `.kiro/` directories

People who liked this also viewed

6 picks

Type