Menu
SkillsMP has collected 11 skills from betsalel-williamson/Templating-Engine. Open a skill to review its source and details.
Showing 11 of 11 collected skills.
Generate TypeScript source files from legacy template meta-patterns using @bwilliamson/template-engine-core at build time (parseLegacy + createSecureEvaluator). Use when building apps via template→code expansion — calculator-cli dogfood, SQL/config…
Build toward the paper V2 templating language using host-layer contracts, Mustache logic-less presentation, and TrustedTemplate fail-closed rules. Use whenever implementing V2 engine slices, TrustedTemplate, FunctionRegistry, or dogfood build-toward-V2 tasks…
MDCP Helper: Act as an expert Systems Architect to draft and design system architecture using MDCP shards.
Use when the work item is documentation-only: authoring or refactoring MDCP shards, fixing stale client/feature/developer docs, removing planning backlogs from durable shards, or when the user asks for a technical-writer pass without product-code changes.
MDCP Helper: Act as an expert Software Engineer to implement and document new features using MDCP shards.
Use when bootstrapping MDCP in a greenfield or brownfield repository, first-time setup of sharded docs, migrating legacy markdown into MDCP guides, getting started with an MDCP documentation pipeline, or onboarding onto MDCP helper skills for a first feature.
Documentation system Agent Skill for MDCP (MarkDown Context Protocol): keep specs, architecture notes, and product ideas in small Markdown shards so docs stay maintainable as ideas keep arriving. Teaches agents docs-as-code discipline — update shards before…
MDCP Helper: Act as an expert UX Designer for user-centric design — end-user value, processes, and workflows in MDCP shards (interfaces when they serve those flows).
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when creating new skills, editing existing skills, or verifying skills work before deployment