arch

"This skill should be used when the user needs to design or iterate on system architecture — technology stack, external dependencies, component design, information flows, interface contracts, and test strategy. Common triggers include: 'architecture', 'design the system', 'component design', 'tech stack', 'how should we build this', 'system design', 'interface contracts', 'test strategy', 'what tools should we use'. Writes the result as a4/architecture.md (wiki page) following the spec-as-wiki+issues layout."

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 "arch" with this command: npx skills add studykit/skillsmp-studykit-studykit-arch

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.

General

ci-setup

This skill should be used when the user needs the LLM to set up or update the CI / test environment — installing test runners (unit + integration), creating runner configuration, writing one minimal passing test per tier, wiring task entry points, and writing a4/ci.md as the test-execution reference. Common triggers include: 'set up testing', 'add integration tests', 'set up CI', 'write ci.md', 'update test environment'. Re-callable any time test infrastructure evolves.

Repository SourceNeeds Review

-0studykit

General

domain

"This skill should be used when the user needs to extract or revise the cross-cutting Domain Model — concepts, relationships, state transitions — from an existing use-case set. Common triggers include: 'domain model', 'extract concepts', 'glossary', 'class diagram', 'state diagram', 'concept relationships', 'state transitions', 'domain.md', 'reconcile vocabulary'. Writes a4/domain.md (wiki page) following the spec-as-wiki+issues layout. Authored separately from usecase: usecase captures per-UC actor/situation/flow; domain extracts the cross-cutting vocabulary that emerges across UCs."

Repository SourceNeeds Review

-0studykit

General

usecase

This skill should be used when the user has a vague idea for software but doesn't know exactly what to build, when the user says 'help me figure out what to build', 'what should I make', 'shape this idea', 'use cases', 'gather requirements', 'what do users need', 'break this down', or when a rough idea needs to be shaped into concrete Use Cases through a Socratic interview. Writes per-UC issue files plus wiki pages into <project-root>/a4/ following the spec-as-wiki+issues layout.

Repository SourceNeeds Review

-0studykit

General

brainstorm

This skill should be used when the user wants to brainstorm, generate ideas, explore possibilities, or think through options. Triggers: 'brainstorm', 'generate ideas', 'think of options', 'explore possibilities', 'creative thinking', 'what are some ideas for', 'help me think about'. Assesses the situation and selects the appropriate technique — SCAMPER, Free Brainstorming, Mind Mapping, Reverse Brainstorming, Random Stimulus, and more.

Repository SourceNeeds Review

-0studykit