Some checks failed
validation / verify (push) Failing after 13s
- Schema review: a dotted path is judged only when it starts at a name the resource type has, so a database flag or a service name is no longer read as a missing setting. Lesson L-04, which worked around that, is retired. - Skill routing: in a Change request the question says what changed. - Evaluation: a case may list code_standards the infrastructure code must meet; case 06 checks its overlay's regions, naming and labels. - Model tiers (iteration 5 step 6): a lighter model for a role's first attempt, named in the provider bundle. Measured on case 03 and left off: Flash saved five cents on the IaC author and took twice the requests. - Steps 7 and 9 decided against on the numbers, recorded in the plans. - Plans: the runs of cases 05 and 06, and the first proof of the lessons on case 03 (no Revision, 22 minutes against 28, quality held). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| google-cloud-lessons | Rules learned from earlier solution-architecture work on Google Cloud, one set per Deliverable. Each was proposed from problems that recurred across Executions, approved by a person, and kept only while evaluation shows it helps. Use before drafting a Deliverable, to read the lessons for that Deliverable and follow them. |
|
Lessons
Each reference below holds the lessons for one Deliverable. Read the one for the Deliverable you are producing, with load_skill_resource, before you draft, and follow every rule in it that applies. A rule here takes precedence over a general habit; your role's instructions and the contract submit_deliverable checks take precedence over a rule here.
| Deliverable | Reference | Lessons |
|---|---|---|
| deployment guidance | references/deployment_guidance.md |
1 |
| target architecture | references/target_architecture.md |
4 |
This Skill is written by the lessons loop (app/learning/), from proposals a person approved. Do not edit it by hand: change the proposal and publish again.