Keyword SPEC
Five Claude Code habits for spec-first development
Interview first, use subagents, set up hooks, rewind with checkpoints, and review with a fresh subagent.
Setting up and running Claude Code: settings, permissions, skills, hooks and slash commands. Each post has the exact config to copy.
Keyword SPEC
Interview first, use subagents, set up hooks, rewind with checkpoints, and review with a fresh subagent.
Keyword DRAW
Install one skill for the visual you need and inspect its scripts before granting access.
Keyword STARTER
Give your skill a specific name and trigger description, then move detail into linked files.
Keyword HOOKLIGHT
Choose events for working, permission requests and completion without granting permissions automatically.
Keyword SLIDES
Choose web slides, editable Office files or Markdown exports before installing a presentation tool.
Keyword SHEETS
Use SQL, CSV tools or a notebook for the calculation, then review what your agent sends to its model.
Keyword BRANDKIT
Choose a design reference, import its assets and review the result before reusing it.
Compare the reported historical upload behavior with the consent flow in the version you install.
Keyword AUDIT
Install Claude SEO and run a scoped audit; its findings still need a human review.
Review the renamed plan, verification conditions and current billing before changing subscriptions.
Use EGM to draft a specification and have fresh reviewers question its assumptions.
Keyword BOTHSIDES
Write your choice before asking an agent for both arguments; the study does not prove this prevents bias.
Keyword MARKETING
Install skills for copy, landing pages and email, then review their output against your sources.
Keyword SPRINT
Use gstack's planning, review and QA skills in order, after reviewing the installer's hooks.
Keyword STACKPICK
Cost, context, repo packing, browser debugging, diff review and PR review: one tool each, with the install line.
Keyword ENVLOCK
Four steps that stop Claude Code reading your secrets, and the check that proves it worked.
Keyword IDLE
Choose whether long idle conversations compact automatically, with the documented version and cache limits.
Keyword TOKENCUT
Try RTK, Headroom or Context Mode, with usage checks before you trust their token savings.
Keyword APPROVE
Reduce routine approval prompts while keeping documented permission rules and review limits.
Keyword EXTENSION
Use Cursor's incident checks and remediation guidance; removing the extension alone may leave persistence.
Keyword HALLMARK
Install Hallmark and audit before redesigning, with separate requirements for browser checks.
Keyword WEEKLY
Review the 2.1.309 and 2.1.311 fixes for long sessions, stale instructions, MCP tools and sandbox behavior.
Keyword WHEREPUT
CLAUDE.md can't enforce never. Hooks, skills, rules and subagents can, and here is when to use each.
Keyword DSPACK
Start with a reviewed design reference, import its rules and check one generated page before reusing it.
Keyword OPENSAFE
Inspect hooks and editor startup configuration before a cloned repository can execute commands.
Keyword PLUGPICK
Install the plugin that matches your work, after reviewing its code and permissions.
Keyword VIDEO
Start a Remotion project, time spoken words and prepare assets before rendering your video.
Keyword TREE
Give parallel sessions separate files and branches while keeping their shared repository history.
Build a queryable graph of a repository and inspect the source behind its connections.
Keyword MEMORY
Keep a short CLAUDE.md for recurring project facts, then check which instructions loaded.
Give a review subagent only the file-reading tools it needs.
Keyword DESIGN
Use separate guidance for visual direction, components, motion and interface review.
Keyword HACKS
Inspect context, ask side questions and review changes without installing another plugin.
Choose the right hook event, preserve existing settings and check that the action actually runs.
Try the Ponytail skill on a small change and review what it reuses before accepting the result.
Keyword SEO
Match site audits, AI search, schema, page templates and blog writing to documented Claude Code workflows.
Choose a server for repository work, browser checks, library docs, error reports or workspace notes.
Create a small skill, choose its scope and verify it against a known file change.
Keyword SKILLS
Install skills for planning, design, testing and documents, then check their work on a small task.
Opus 4.6 expanded context capacity, but useful inputs and review still determine the outcome.
The December 2025 announcements explain Bun's role in Claude Code and the commitments to its open-source project.
Anthropic emphasized coding and agent work, alongside changes to Claude Code and the API.