shiro
CLAUDE.md1 starsChanged 9 days agoMITView on GitHub
A job-application workspace for Claude Code. There are no API keys: everything runs on the user's own Claude subscription.
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Truth: Never invent or inflate experience, skills, numbers, dates or titles, whether in resumes, form answers or drafts.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shiro
A job-application workspace for Claude Code. There are no API keys: everything runs on the user's own Claude subscription.
Commands
/setup [resume]: create the private career memory from the user's resume and collect standard form answers./review [JD path | URL] [resume]: 10 reviewers try to reject the resume in parallel → debrief → the resume writer produces a tailored version./apply <URL> [resume]: fill an application form in Chrome from memory. Never submits./remember <fact>: save a new career fact to memory.
Layout
.claude/agents/:resume-picker(chooses the best base resume for a job), the panel reviewers (ats,recruiter,hiring-manager,teammate,rival-applicant,ceo,technical-interviewer,skeptic,skip-level-manager,hr-screener), plusdebriefandresume-writer..claude/skills/: the four commands.ui/review-pipeline.mjs: how the app runs a review: free local steps (JD, resume text viatools/resume-text.mjs, keyword pre-rank, files,tools/resume-html.mjs+ PDF) plus oneclaude -p --agent <name> --tools ""call per agent with inputs inline. Agent files therefore support two modes: inline (reply with the output) and file paths (read/write files, used by the/reviewskill in the terminal).ui/memory-edit.mjs: free removals from the Memory tab (an item of a memory file, a document, a link, a resume). It saves the touched files tomemory/.trash/<id>/first so Undo restores them exactly; the trash is emptied on server start and after an hour. Agents ignorememory/.trash/. Free-text "Forget" goes to Memo as/remember FORGET: ….ui/: the local web app (npm run ui).server.mjsrunsclaude -pwith stream-json and turns its events into UI events;public/is plain HTML/CSS/JS with no build step. The app's agent names and the reviewer list inui/public/creatures.jsmust match the agent files.templates/memory/: blank memory files.templates/resume.htmlandtemplates/cover-letter.html: printable templates.tools/html-to-pdf.mjs: turns a run's HTML into a PDF with the local Chrome/Edge (node tools/html-to-pdf.mjs <in.html> <out.pdf>, files must be in runs/ or memory/). Pages with<meta name="shiro-fit">(the resume template) are fitted: if the PDF spills onto an extra page it tightens size and spacing step by step (never below ~9pt) and writes the chosen step into the HTML too.tools/resume-html.mjsturns bare URLs, emails and the contact line's addresses into blue links. Skills call it as a single command with nocd, because the app only pre-approves that exact command prefix.tools/file-doc.mjs: moves a file insidememory/into its section (node tools/file-doc.mjs <file> <section>/<clear-name> …), never overwriting. Sections: certificates, academic, letters, portfolio, cover-letters, other, duplicates, resumes.memory/documents/<section>/+memory/documents.md(one heading per section, plus Links): files and links that forms may ask for;/applyuploads from here. Files directly inmemory/documents/are new and unsorted. Never identity or bank documents.ui/server.mjsVERSIONmust equalAPP_VERSIONinui/public/app.js; bump both when the server changes, so a stale running server shows a restart banner.memory/: the user's career memory (private, git-ignored). The source of truth for everything about the user.runs/: one folder per/reviewrun (private, git-ignored).
Rules that always apply
- Keep memory current. Whenever the user mentions a new career fact in any conversation (started or finished an internship or job, completed a course or certificate, built a project, learned a skill, won something, changed phone, email, location or status), update
memory/following.claude/skills/remember/SKILL.md, and tell them in one line what was saved. - Truth. Never invent or inflate experience, skills, numbers, dates or titles, whether in resumes, form answers or drafts. Ask for missing facts; don't guess them.
- Never submit applications. Fill only; the user reviews and submits. Never create accounts, type passwords, solve CAPTCHAs or accept terms on the user's behalf.
- Privacy.
memory/andruns/hold personal data. Never commit them, and never send their contents anywhere except the application form the user asked to fill. Never store passwords, government ID numbers or bank details. - Which source wins. Memory is the source of truth. When a resume and memory disagree, memory wins, unless the resume has something newer than memory's
Last updateddate (inmemory/profile.md) that memory doesn't have yet (for example a new internship that started after that date). Then the resume wins for that fact: use it, and save it to memory following the remember skill. Among resumes, theReference resumeinprofile.mdbeats the others. - Keep the repo generic. Agents, skills and templates are shared with other users, so personal details stay out of them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

