See which page ranks for each query with the Search Console API.
Use the Search Console API to retrieve page and query together and check which URLs appear for each term. The returned rows can reveal overlap between your pages.
Codex vs Claude Code: two agents on one codebase
I run Claude Code and Codex daily, sometimes on the same repository. My session logs show the context cost, while the working tree shows the coordination cost.
What using Claude Code actually looks like
Using Claude Code is a loop: ask, change, check, decide. Here is what a normal session looks like, six commands worth learning first, and how to recover when it goes wrong.
Claude Code skills: building a workflow that runs itself
The control layer of my work system is markdown and small scripts. How a workflow combines Claude Code skills, rules, model routing, and parallel sub-agents.
Splitting an AI pipeline between Python scripts and the model
Python handles parsing and deduplication in my inbox pipeline. The model gets the prepared text and extracts summaries, decisions, and action items.
The Claude Code plugins I built and run
I put the Claude Code tools I reuse across projects into one public toolshed: generators, workflow commands, anti-slop checks, search visibility, rule packs, and prompts.
My AI was smart. It just couldn't see my job.
My work context was scattered across email, meetings, documents, and notes. So I wired it into a private Obsidian vault Claude Code can read.
Four calendar days, one person, one full redesign
A full site redesign in four calendar days, from design system to admin stack. The real question is what product teams should do with the time AI gives back.
A safe way to edit database content with AI coding tools
AI coding tools edit files. Your content lives in a database. This is the pull, diff, push workflow that connects the two without hand-writing SQL against production.
How I built this site with Claude Code.
I built the first version of this site over about three weeks of work with Claude Code. The build story covers the architecture, review workflow, and decisions I still owned.
Claude Code and the context window on bigger projects
My website is close to a thousand files. I keep Claude Code useful by giving each session one task, naming the files involved, and keeping the project instructions current.
Fixing bugs with Claude Code (without losing your mind)
Something broke. Describe what you expected, show what happened, let Claude investigate, then test the proposed fix.
Claude Code permissions: what to allow and what to block
Claude Code can change real files and run commands. Check the permission mode, protect secrets, review the diff, test the result, and keep a restore path.
What is vibe coding, and when should you use it?
Vibe coding is useful for disposable experiments where failure is cheap. Software you intend to keep needs review, tests, version control, and an owner.
Keeping your Claude Code project organized
Give each file an obvious home, document the stable rules, and test what your deployment actually includes.
Teaching Claude Code your standards with rule files
Use CLAUDE.md for project-wide facts and rule files for detailed standards, including rules that load only for matching paths.
Creating reusable Claude Code skills
If you keep pasting the same prompt, save it as a small Claude Code skill. You can run it with a short command and add templates or scripts later.
The CLAUDE.md file: what to put in it, and what to leave out.
Each Claude Code session starts with fresh context. CLAUDE.md loads the project facts and instructions you want available, while auto memory stores patterns Claude learns.
How to undo Claude Code changes with rewind and Git
Claude Code will sometimes make the wrong change. Inspect the diff, use rewind for recent mistakes, and keep Git for a durable restore point.
Set up Claude Code so you can review changes as they happen
Keep Claude Code and the result visible at the same time so you can review each change before asking for the next one.
How to use Claude Code subagents for parallel work
Use Claude Code subagents when a focused task can stand alone. Split independent checks, ask for one combined result, and keep dependent work with one owner.
Giving Claude Code better instructions
Give Claude Code the problem, relevant context, and the result you expect. A specific instruction reduces guessing, but you still need to review the result.
How Claude Code sees your files
The folder where you start Claude Code is its main working directory. Keep one project in scope, then add other directories only when the task needs them.
Your first conversation with Claude Code
Create a separate practice folder, then use three prompts to inspect it, create a file, and edit that file while reviewing each action.
Installing Claude Code without the old Node.js setup
Install Claude Code with Anthropic's current native installer on Windows, macOS, or Linux. No Node.js, no npm, and the fixes for when the command is not found.
Opening the terminal for the first time
You need four terminal actions to start Claude Code: open it, run a command, move to the project folder, and close it when you are done.
What Claude Code can do with your project
Claude Code can inspect a project, use development tools, and apply approved changes. Your job is to decide what should happen and check the result.
/agent-usage-counter
Count local Claude Code and Codex token usage without uploading prompts, paths, or session text.
/a-rules-optimizer
Check CLAUDE.md and project rules against the codebase, then fix stale references and missing guidance.
/a-self-learner
Review recurring code review findings and propose changes to project rules, review skills or automated checks.
/a-seo-gsc
Analyze Google Search Console data and prioritize page and query issues using computed evidence.
/a-geo-optimizer
Audit crawler access, structured data and page content for AI search visibility.
/a-review-optimizer
Create or improve a code review skill using your project structure, conventions and known review gaps.
/a-unslop-ui
Review a website for common AI design patterns and make deliberate choices about its layout, typography and color.
/a-unslop-code
Review AI-written code for bugs, unnecessary complexity and cosmetic issues, with bugs checked first.
/a-unslop-text
Review AI-sounding prose for generic wording, repeated patterns and voice consistency.
search-visibility
Two Claude Code skills to analyze Search Console data and audit pages for AI search visibility.
flutter-rules
Claude Code rules for Flutter and Dart, covering state and navigation with Riverpod and GoRouter examples. Use alongside the generic pack.
react-ts-rules
Claude Code rules for React and TypeScript, covering components, forms and data fetching. Use alongside the generic rules pack.
generic-rules
Claude Code rules for security, code quality, architecture and CSS. Use this baseline alongside a language pack.
php-rules
Claude Code rules for PHP 8.2+, covering types, database access and security. Use alongside the generic rules pack.
python-rules
Claude Code rules for Python 3.10+, covering types, logging, subprocesses and security. Use alongside the generic rules pack.
dev-loop
Fix bugs, review changes and prepare commits with Claude Code commands that use your project conventions.
sanitize-public
Scan a repository or bundle for credentials and private details before publishing, then review what the scanner cannot detect.
dev-workflow-forge
Build review skills and project rules for your codebase, then use review history to propose improvements.
unslop
Three Claude Code skills for reviewing AI-generated writing, code and website design, with scanners and manual checks.
role lenses
Six Claude Code commands for reviewing architecture, product decisions, design, operations and implementation.
a-make-prompt
Turn a rough request into a prompt with a defined output, relevant context and checks for completion.