platform-builder

Extend Copier template platform slices with docs and validation.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/mo0rti/prism --skill platform-builder-mo0rti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-builder
Source: https://github.com/mo0rti/prism/tree/main/.agents/skills/platform-builder
Command: npx skills add https://github.com/mo0rti/prism --skill platform-builder-mo0rti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add or extend a platform slice in this Copier template repo by following the current repo docs, matching established template patterns, updating docs and AI context, and validating generation. Use when working on backend, web-user-app, web-admin-portal, mobile-android, or mobile-ios template support.

Core Features & Use Cases

  • Edit the platform files under template/{platform}/, keeping Jinja syntax balanced and using .jinja extensions only when needed.
  • Update platform docs under template/{platform}/docs/ and refresh AI context references such as CLAUDE.md.jinja, AGENTS.md.jinja, and related wiring.
  • Validate and wire changes across shared wiring as required, ensuring maturity language is explicit (implemented, partial, experimental, or planned) to support end-to-end template generation scenarios.

Quick Start

Apply platform-builder to add or extend a platform slice by following the repository docs and updating templates accordingly.

Frequently Asked Questions about platform-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extend a Copier template to support a new platform slice?

To extend a Copier template with a new platform slice, add or refine files under template/{platform}/, update the related documentation in template/{platform}/docs/, and validate generation to ensure proper wiring and balanced Jinja syntax.

What's the best way to update AI context files when modifying Copier platform templates?

Update AI context files in Copier platform templates by refreshing references like CLAUDE.md.jinja and AGENTS.md.jinja under template/{platform}/docs/, ensuring all wiring updates are mirrored in the template files.

Does platform-builder work with both web and mobile Copier template platforms?

Yes, platform-builder applies to backend, web-user-app, web-admin-portal, mobile-android, and mobile-ios Copier template platforms, guiding file placement and documentation updates across these specific platform slices.

How do I validate Copier template generation after adding a platform slice?

Validate Copier template generation by ensuring files are correctly placed under template/{platform}/, Jinja syntax is balanced, and shared wiring updates are applied with explicit maturity language like implemented, partial, experimental, or planned.

When should I use .jinja extensions for files in a Copier platform template?

Use .jinja extensions for files in a Copier platform template only when needed to preserve Jinja syntax processing, keeping the template/{platform}/ structure balanced and ensuring proper end-to-end generation scenarios.