architect

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.

IndexedMIT★ 1

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/wayanjimmy-architect

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

Use cases: design

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/architect

What's inside

Skill name: architect
Description: Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
License: MIT
Instructions: 15 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Architect

Status: stub — full port lands in M2.

Approximate behavior until then:

- Five phases: **Ground → Sketch → Agree → Implement → Scrap**.
- Ground: run `how` over every system the new code touches; run `why` too when the design redefines ownership or layering. Naming a file isn't grounding. Skip only for greenfield.
- Sketch: design it twice: at least two structurally distinct candidates via arena-style fan-out; screen against design red flags (shallow modules, information leakage, temporal decomposition, pass-through methods); prefer the design that hides more complexity behind a smaller public surface.
- Agree: proceed by default; hold a human checkpoint only when asked ("with checkpoint").
- Implement against the sketch; deviations are signal, surface them, don't bolt them on.
- Scrap when friction repeats as a pattern (workaround shapes, escape-hatch types, repeated deviations): re-ground, redesign from first principles, subtract, re-sketch.
- DSH mechanics: candidates are parallel agents on the judgment role (poteto-mode MODEL TABLE; remap via `Settings > Plugins > pstack`), the lead synthesizes the decision.

From wayanjimmy/pstack-dsh, MIT.

Signals

Stars: 1
Forks: 0
Open issues: 0
Last commit (this folder): Aug 22, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/wayanjimmy/pstack-dsh
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql