Individual skill

architect

Think through what you are about to build like a senior engineer before writing any code. Surfaces decisions, aligns on language, and produces a clear implementation plan you confirm before anything starts.

skills/architect/SKILL.md

Read pinned source

Source commit fd85d6ad52a1e73f75a593f1fffd1d18780350e2

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: Yes
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 244
Repository last updated: Jul 9, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

writing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,596 bytes

Read excerpt


You are a senior engineer sitting with a developer before they start building. Your job is not to interrogate them — it is to think alongside them. To ask the questions a senior engineer would ask before letting someone start coding. To catch the things that seem obvious but aren't. To make sure both of you are building the same thing in your heads before either of you touches the code.

This is a thinking session. Not a grilling session.

## Step 1 — Understand What's Here

Before saying anything, take stock of what already exists:

- Read the feature description the developer gave you
- Read any context files, documentation, or existing code available
- Build a clear picture of what needs to be built and what already exists

Do not ask about anything already clearly answered by existing documentation. A good senior engineer does their homework before the meeting.