architect

Turn an approved spec into a module layout: named modules, public interfaces, data flow, error channels, dependency choices. Produces a design doc (markdown) plus interface-stub files (function signatures with `throw new Error("not implemented")` bodies) so downstream `implement-*` modalities can execute against a published contract. Use when a spec exists and the next question is "what shape of code." Do NOT use when no spec exists (send to `/safer:spec` first), or when the work is obviously one-module (send to `/safer:implement-junior`).

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "architect" with this command: npx skills add chughtapan/skillsmp-chughtapan-chughtapan-architect

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Coding

orchestrate

Decompose a multi-step intent into sub-tasks, classify each by modality, route each sub-task to the right modality skill, gate every handoff on a published artifact, and track the whole pipeline via GitHub issues. Use when a goal spans more than one modality (not just implementation, not just investigation, not just research) or when sub-tasks have dependencies that need sequencing. Do NOT use for single-modality work — invoke the modality directly. This skill is the VP of Engineering.

Repository SourceNeeds Review
-0chughtapan
Coding

research

Run an iterative hypothesis loop on an open question with no known answer. Produces a ledger of claim, evidence, experiment, insight, and confidence for every round, closing with a final report of validated insights. Use when the question is open-ended ("how do X systems handle Y?", "why does Z regress under load?"), when literature review is load-bearing, or when the next step depends on answers the team does not have yet. Do NOT use when the question is a yes/no feasibility probe (route to /safer:spike) or when the work is to ship code (route to /safer:spec or /safer:implement-*).

Repository SourceNeeds Review
-0chughtapan
Coding

typescript

TypeScript craft floor. The concrete projection of PRINCIPLES.md principles 1 through 4 onto TypeScript code. Invoked in-context by the implement-* skills when the target repo is TypeScript. Encodes the ideal repo state, the decision table between human-era shortcuts and agent-era full versions, the phrases that signal a shortcut is about to happen, and the mapping from eslint-plugin-agent-code-guard rules back to principles. Auto-applies when writing or reviewing .ts files outside of a /safer:spike branch.

Repository SourceNeeds Review
-0chughtapan
Coding

dogfood

Read any published artifact (spec, design doc, PR body, issue comment, investigation writeup) with NO prior session context and report on how a cold-start consumer would feel picking it up. Scores four numeric axes (clarity, completeness, actionability, trust) plus a friction list with evidence, emits a SHIP / REVISE / REJECT verdict, and publishes the report back to the artifact's GitHub thread. Use when an artifact is about to be handed off and you want a portability check before the next modality runs. Do NOT use to rewrite the artifact; this is a reading modality, not a writing one.

Repository SourceNeeds Review
-0chughtapan