agentleFS
Sign inStart free
rizukirrrizukirr/vibekit/skills/quick/SKILL.md

quick

Skill20 starsChanged 3 months agoMITView on GitHub

Use when the user types /vibekit:quick: writes the change immediately under lazy's ladder, no spec, no plan, no subagents. Reports what it skipped.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plant-seed, discuss and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • notqueSkill

    plant-seed

    Capture forward-looking idea as a seed for future feature design.

    Also in 3 projects that use this

  • markmdevSkill

    discuss

    Discuss a problem with other AI agents before implementing. Spawns one or more autonomous claude -p conversations with different perspectives (architect, critic, domain expert), runs multi-round discussions, and synthesizes findings. Use when facing design decisions, architecture tradeoffs, knowledge organization questions, or any problem that benefits from multiple viewpoints before committing to an approach. Also use proactively when you're uncertain about a direction.

    Also in 4 projects that use this

  • VercelSkill

    next

    Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 6 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 4 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Distinctive:

    Check before writing. Each of these is a fact about the change, not a judgement about its size:

    line 21

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

quick

The fast path. One intent in, the change written now.

The waiver

brainstorm, plan, exec and verify do not apply here. No spec doc, no plan doc, no subagent dispatch, no verification report. That is the whole point of typing this instead of /vibekit:vibe.

Invoke lazy and write under its ladder. Do not restate its rungs: one copy of the ladder exists, and it lives in lazy.

Bail out first

Check before writing. Each of these is a fact about the change, not a judgement about its size:

  • It needs a dependency that is not already installed.
  • It touches a schema, a migration, or the shape of stored data.
  • It touches auth, payments, permissions, or any other trust boundary.
  • It spans more files than you can hold in one reading.
  • The intent reads two ways.

Any one of them: stop, name the criterion that tripped, and say the request wants brainstorm. Do not start a spec yourself, and do not negotiate: the user asked for speed, and the honest answer is that this is not the path for it.

None of them: write the change now.

The floor still holds

Nothing runs behind you, so lazy's never-simplify-away list is not optional here: validation at trust boundaries, error handling that prevents data loss, security, accessibility, and anything the user explicitly asked for.

Non-trivial logic leaves one runnable check, and you run it. verify is not coming. A change you did not execute is a change you are guessing about, and "evidence or it did not happen" is not waived by speed.

debug is not waived

A failed check routes to debug exactly as it always does. quick skips the gates before implementation. It does not skip the one after a failure.

Say what you skipped

Close with one line naming the skipped stages and the check you ran, so a fast path never reads like a verified one:

Skipped: brainstorm, plan, exec, verify. Ran: <the check, and its result>.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free