0 Fork 0

mirror of https://github.com/affaan-m/ECC.git synced 2026-10-26 18:35:05 +00:00

Files

T

Eric BellavanceandClaude Opus 5.5 1e895858d0 docs(kiro): use always inclusion for always-on steering files

Kiro only loads steering files automatically in every conversation when
they use `inclusion: always`; `auto` loads them only when the request
matches the description. Switch the always-on steering files to
`always` and update README, install.sh and docs accordingly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-01 13:23:13 -04:00

1.2 KiB

Raw Blame History

inclusion, name, description

inclusion	name	description
always	patterns	Common design patterns including repository pattern, API response format, and skeleton project approach

Common Patterns

Skeleton Projects

When implementing new functionality:

Search for battle-tested skeleton projects
Use parallel agents to evaluate options:
- Security assessment
- Extensibility analysis
- Relevance scoring
- Implementation planning
Clone best match as foundation
Iterate within proven structure

Design Patterns

Repository Pattern

Encapsulate data access behind a consistent interface:

Define standard operations: findAll, findById, create, update, delete
Concrete implementations handle storage details (database, API, file, etc.)
Business logic depends on the abstract interface, not the storage mechanism
Enables easy swapping of data sources and simplifies testing with mocks

API Response Format

Use a consistent envelope for all API responses:

Include a success/status indicator
Include the data payload (nullable on error)
Include an error message field (nullable on success)
Include metadata for paginated responses (total, page, limit)

1.2 KiB Raw Blame History