write-for-ai
openbooklet.com/s/write-for-aiopenbooklet.com/s/write-for-ai@1.0.0GET /api/v1/skills/write-for-aiWrites documentation, commit messages, and PR descriptions optimized for the NEXT AI session to understand the project cold. Templates for README, CLAUDE.md / AGENTS.md, conventional commits, and PR bodies. Prioritizes tables and checklists over prose, absolute file paths over vague references, invariants over narrative.
Turns improvement intent into shipped versions, deterministically: *intent â issues â milestones = versions â tagged release*. Direct-call only. Given a backlog (pasted notes, a `/vibesubin` sweep report, or a named scope), this skill writes a well-specified bilingual issue set, clusters items
This doc is canonical. If ADDING-A-SKILL.md and CLAUDE.md ever disagree on skill-authoring mechanics, CLAUDE.md wins on policy (what invariants exist) and this file wins on mechanics (what files and sections are needed). Both must stay in sync on category caps (10 + 1).
A thin, deliberately host-specific wrapper for one workflow: *"I've finished a batch of edits â run Codex for a second-model review, feed the findings back, let Claude resolve them with verification."*
Repos don't break in a day. They rot over months as dead code accumulates, god files grow, hardcoded paths get committed, and six-month-old `TODO`s turn into forever-`TODO`s. This skill surfaces what's rotting â it never edits code.
Repos don't get slow from code. They get slow from binaries â a PDF committed last year, a 400 MB SQLite file a junior engineer checked in, a `node_modules/` that snuck past `.gitignore`, a `dist/` directory nobody bothered to exclude. A single 200 MB blob in git history turns `git clone` into a c
The operator has to make structural decisions every week: where does this value live? Should I pin this dependency? Is this `.env` entry right? Which branch should I work on? Each decision is a small tax on their attention. This skill pre-pays that tax with one opinionated answer per question.
Every project has two kinds of structural decisions. Some are low-stakes â which branch naming, which directory layout â and a mistake costs a little friction. Some are high-stakes â where a database password lives, whether `.env` is tracked, whether a production token is in a build-time varia
The operator asked for a change that's supposed to preserve behavior â a refactor, a rename, a split, an extract, a dead-code deletion. Your job is to *prove* that behavior was preserved, not just produce a diff that looks right.
Most vibe-coder web projects start with a template, get rushed into production, and end up with two versions of every button, three shades of "primary blue", spacing values that were eyeballed to the nearest pixel, and a navigation bar that doesn't match between two of the pages. None of those are b
Auto-indexed from subinium/vibesubin
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.