bruce48x/Lakona / .agents/skills/lakona-architecture-review
lakona-architecture-review
VerifiedPerform an explicitly requested, read-only Lakona architecture and framework-health review; honor any specified reduced scope.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
| agents/openai.yaml | config | 357 B |
| references/contract-evolution.md | markdown | 840 B |
| references/generated-projects.md | markdown | 1.1 KB |
| references/macro-architecture.md | markdown | 810 B |
| references/micro-code-smells.md | markdown | 1.5 KB |
| references/operability.md | markdown | 835 B |
| references/performance.md | markdown | 1.8 KB |
| references/reliability.md | markdown | 1.1 KB |
| references/reporting.md | markdown | 2.9 KB |
| references/scope.md | markdown | 2.8 KB |
| references/standards-checklist.md | markdown | 8.7 KB |
| references/standards-pass.md | markdown | 3.1 KB |
references/generated-projects.md
View on GitHub# 3. Generated-Project Experience
Treat generated projects as the strictest consumer test.
1. Read the current project-tooling authorities and discover the supported
starter families and defaults.
2. Generate representative current default projects under the repository
root's `.tmp/` review directory.
Cover every supported client family when local tools permit it.
3. Inspect direct and transitive package dependencies, version declarations,
generated project references, build assets, default files, and concepts
exposed to users.
4. Simulate a package upgrade far enough to count the files, versions, and
coordinated changes a user must make.
5. Build or run focused scaffold validation when feasible. Request required
restore or external-tool permission instead of silently skipping it.
6. Record unavailable tools or blocked validation as coverage limitations.
Look specifically for dependency fan-out, independently versioned assets with
one owner, redundant packages, leaked implementation packages, multiple version
authorities, and starter concepts that do not earn their user-facing cost.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |