Skip to content

[P1][Tier 1] Document end-to-end dev recipes for recurring change types #3278

Description

@phenning

Tier 1 — Foundation readiness · Priority: P1

Gap

Some recurring changes are covered by skills (adding-brokered-service, extension-development-host, running-integration-tests), but there is no consolidated set of step-by-step recipes for the FC's common change types showing where to add code, how to wire it in, and how to test it (e.g. add a command, add a setting, add a native AOT addon method, add an integration test scenario).

Investment

  • Document recipes for the top recurring change types, each linking to the relevant skill and test command.

Acceptance criteria

  • Recipes exist for the FC's most common change types.
  • Each recipe shows add → wire → test and links to an existing skill where one exists.

Part of epic #3273

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions