newheap-platform-development

Files (4)

• SKILL.md
• openai.yaml · agents/
• immutable-evidence.md · references/
• platform-fit.md · references/

SKILL.md (first lines)

# NewHeap Platform development

Route the current consumer task to the smallest applicable internal module. Read that module's `SKILL.md` completely before acting:

- [foundation](../newheap-consumer-development/SKILL.md) for bootstrapping, inspecting, repairing or upgrading a consumer repository;
- [backend](../newheap-backend-development/SKILL.md) for .NET foundations, modules, models, services, controllers, Scalar contracts, partial updates, units of work, and AI assistants, agents, tools and model profiles;
- [frontend](../newheap-frontend-development/SKILL.md) for Angular configuration, collections, lifecycle behavior, modals, toasts and the assistant panel;
- [authentication](../newheap-authentication/SKILL.md) for roles, claims, policies, resource permissions, two-factor authentication, passkeys, authentication overrides and the authorized AI invocation context;
- [database](../newheap-database-development/SKILL.md) for provider-neutral queries, SQL Server and PostgreSQL behavior, and supported read-only investigation of unexpected staging or production data;
- [media](../newheap-media-development/SKILL.md) for media contracts, storage, authorization, uploads and events;
- [background processing](../newheap-background-processing/SKILL.md) for transactional events, jobs, background operations, consumers, notifications and AI work in the background;
- [runtime configuration](../newheap-runtime-configuration/SKILL.md) for appsettings, environment, secrets-path and command-line precedence;
- [testing](../newheap-testing/SKILL.md) for reusable test helpers, NewHeap consumer test boundaries and AI evaluations.

Read multiple modules only when the requested work genuinely crosses their boundaries. Keep the router itself free of domain instructions; the focused modules and their references are the authoritative guidance.

For a non-trivial consumer change, read [platform fit](references/platform-fit.md) before implementing when a reusable or cross-cutting NewHeap capability could plausibly apply, when package or guidance versions may affect the design, or when existing consumer code may duplicate Platform behavior. This check is a decision aid, not a requirement to introduce a NewHeap dependency.

For a request whose answer depends on unexpected persisted state, missing or incorrect records, an API/database discrepancy, or unexplained staging or production behavior, load the database module even when the user does not name a database tool. Before deciding that the checked-in diagnostic contract is missing, make one bounded tracked-file search from the consumer repository root for `**/.newheap/database-read.json`, `**/Tooling/DatabaseRead/README.md`, and `**/Tooling/DatabaseRead/requests/*.json`. When that search finds exactly one catalog, route the task through the database module with the directory containing `.newheap` as the diagnostic working directory, even when the local .NET tool manifest is in an ancestor directory. If the user explicitly names another runtime environment, let the database module apply that environment to the governed profile instead of treating the profile's default environment as an allowlist. Do not load runtime configuration or inspect application code, appsettings, secrets or package internals merely to rediscover the selected profile, connection-string name or JSON request shape. Load runtime configuration only when the bounded search finds no catalog, multiple catalogs remain ambiguous, or configuration itself is the subject of the task. Do not route unrelated code, UI or infrastructure bugs to database diagnostics merely because they occur in staging or production.

For changes to the reusable NewHeap libraries, use the separate `newheap-library-maintenance` skill instead.

From NewHeap/NewHeap-Platform, Apache-2.0.

More from NewHeap/NewHeap-Platform