builder SKILL.md skillA
builder from hamza-ali-shahjahan/hamzaish is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hamza-ali-shahjahan/hamzaish/builder@git:20260528.a4e7dfePins git:20260528.a4e7dfe in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hamza-ali-shahjahan/hamzaish
- Path
_archive/v0/agents/mvp/builder/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260528.a4e7dfe, committed May 28, 2026
- Size
- 2,514 bytes
- Repository stars
- 11
- License
- MIT
Drive Claude Code build sessions inside a product folder. Enforces session discipline: read CLAUDE.md + scope.md first, log decisions after.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Builder ## When you activate User says: "let's build the X feature", "implement Y for product Z", "start the next session on linkedup" You don't WRITE the code yourself — you drive the Claude Code session inside the product folder. If you're being invoked from the factory root, switch context to the product folder before starting. ## What you produce - Working code committed in the product's repo - Updated `products/<name>/decisions/` if any architectural choices were made - A session log appended to `products/<name>/decisions/sessions.md` (one paragraph: what was built, what was decided, what assumption was introduced) ## Protocol — every Claude Code session 1. **Open the product folder.** `cd products/<name>` (or its symlink target). 2. **Read `CLAUDE.md`** to refresh architectural context. 3. **Read `scope.md`** to verify the feature is in scope. If ambiguous → invoke `scope-guardian` first. 4. **Read the last 3 entries in `decisions/`** to know what's recently been decided. 5. **Plan the change.** What files, what tests, what side effects on existing code? State the plan in 3 bullets before touching code. 6. **Implement.** Small commits, descriptive messages. …
Read the whole file at its exact version.
How to install
mdr add hamza-ali-shahjahan/hamzaish/builder@sha256:3882ecd3105a0678The line at the top of this page pins the label git:20260528.a4e7dfe, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dslscwzrkctt6hc5)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2514 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hamza-ali-shahjahan/hamzaish · 11 stars · license MIT · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dslscwzrkctt6hc5 GET https://markdownregistry.com/api/v1/resolve?ref=hamza-ali-shahjahan/hamzaish/builder GET https://markdownregistry.com/api/v1/blob/3882ecd3105a0678f05378083ff6654efaaa0aa08f9d423cc00583081ee29356
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from hamza-ali-shahjahan/hamzaish
Every file in hamza-ali-shahjahan/hamzaish