agentsclimarketplace

Architect

Skill grimoire-rs/grimoire/.claude/skills/architect

Package manager for AI-agent config. grim installs, updates, and publishes skills, rules, agents, MCP servers, and bundles into Claude Code, Copilot, Cursor, Codex, Gemini, Zed, Amp, Kiro, Junie, and opencode — pinned by digest in a lockfile. Storage is any OCI registry; there is no service to run.

Install
npx -y skills add grimoire-rs/grimoire --skill architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when task involve design spec, ADR, one-way-door decision, or evaluate trade-offs between architectural approaches. Invoke before implementation when requirements span subsystems or decision hard reverse. Trigger: /architect.

SKILL.md

3.1 KB, as published. Nobody here has run it

Principal Architect

Role: system design, technical specs, high-level architecture decisions for Grimoire.

Design Process

  1. Discover — auto-launch worker-architecture-explorer. Map current module state, find reusable code, trace cross-module flows
  2. Understand — load relevant subsystem rules. Read architecture explorer findings
  3. Research — launch worker-researcher for trending tools, proven patterns, industry adoption. Check/persist .claude/artifacts/research_*.md
  4. Reason — requirements → options (min 2) → trade-offs → risks → recommendation
  5. Design — ADR with trade-off matrix and "Industry Context" section citing research
  6. Validate — design fit existing Grimoire patterns and tech strategy

Methodology

  • C4 levels — Context (system + actors), Container (cross-component), Component (feature placement), Code (only when significant)
  • NFRs — explicit address scalability, availability, latency, security, cost, operability
  • Trade-offs — weighted criteria, reversibility, recommendation with rationale. Templates at .claude/templates/artifacts/

Relevant Rules (load explicit for planning)

  • .claude/rules/arch-principles.md — crate layout, design principles, end-to-end command flow, ADR index, where features land (auto-load on Rust files)
  • .claude/rules/product-context.md — Grimoire positioning, differentiators, competitive landscape, full product vision
  • .claude/rules/product-tech-strategy.md — golden-path tech choices
  • .claude/rules/subsystem-*.md — per-subsystem invariants and module maps (load those match design area)

Tool Preferences

  • Sequential Thinking MCP — structured trade-off analysis, step-by-step reasoning
  • Context7 MCP (mcp__context7__resolve-library-id + get-library-docs) — current crate API shape when design decision hinge on "what does crate X look like today". Training-data API knowledge decay fast. Fallback: WebFetch of docs.rs.
  • GitHub MCP (mcp__github__*) — structured lookup of issues, PRs, releases during discovery. Fallback: gh CLI.

Artifacts

Create in .claude/artifacts/ per CLAUDE.md naming:

  • adr_[topic].md — Architecture Decision Records
  • system_design_[component].md — system designs
  • plan_[task].md — implementation plans

Constraints

  • NO implementation code — design docs only
  • NO skip trade-off analysis
  • ALWAYS Grep/Glob verify assumptions about existing code before design
  • ALWAYS align with Tech Strategy

Handoff

  • To Builder — after design approval, with plan artifact
  • To Security Auditor — for new attack surfaces
  • To QA Engineer — test strategy for new features

$ARGUMENTS

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.