← all publishers

arndvs

@arndvs source repo

Report this profile Claim this profile

• 40 skills
• 0 followers
• 11 hours ago last updated

1. ▌
   Tdd · arndvs

   Red-green refactor workflow for test-driven development. Use when asked to 'write tests first', 'TDD', 'red-green refactor', 'test-driven', or 'failing test first'. Backend-only — do not use for frontend components.
   0
   installs
2. ▌
   Caveman · arndvs

   Ultra-compressed conversational replies — drops articles, filler, and hedging to cut output tokens while keeping full technical accuracy. Deliverables (plans, PRDs, issues, docs, commits, code) always stay normal prose; only the surrounding narration compresses. Use when asked to 'talk like caveman', 'caveman mode', 'be terse', 'fewer tokens', 'compress your replies', or invokes /caveman.
   0
   installs
3. ▌
   Do Work · arndvs

   Core execution loop for implementing tasks. Use when asked to 'do work', 'implement', 'build this', 'fix this', 'plan execute clear', 'plan then execute', 'work loop', or when working through a plan or backlog item.
   0
   installs
4. ▌
   Explore · arndvs

   Deep codebase exploration using parallel subagents. Use when asked to 'explore', 'understand', 'investigate', 'map out', 'how does X work', or 'audit' a part of the codebase.
   0
   installs
5. ▌
   Document · arndvs

   Write, update, or audit documentation. Use when asked to 'document this', 'write docs', 'update the README', 'add JSDoc', 'write a changelog', or 'create an ADR'.
   0
   installs
6. ▌
   Grill Me · arndvs

   Interview the user relentlessly about a plan or design until reaching shared understanding. Use when asked to 'grill me', 'interview me', 'ask me questions about this', or before writing a PRD to flesh out vague ideas.
   0
   installs
7. ▌
   Research · arndvs

   Cache expensive exploration into a research document before building. Use when asked to 'research', 'investigate before building', 'gather context', 'flush unknowns', or before a large feature where unknowns need flushing.
   0
   installs
8. ▌
   Architect · arndvs

   Comprehensive implementation planning with vertical slices. Use when asked to 'act as an Architect', 'plan this', 'create an implementation plan', 'slice this into tasks', or when a task needs decomposition before execution.
   0
   installs
9. ▌
   Mobile Dev · arndvs

   Expo mobile development workflow — clean state reset, startup sequence, native rebuild decisions, and Android emulator/QEMU troubleshooting for Launch Core and its forks (Foreword, Scorpion, Aligned, Cast).
   0
   installs
10. ▌
    Code Review · arndvs

    Focused review of staged or recent changes to find edge cases, logic errors, and integration risks before merging. Use when asked to 'do a code review', 'review my changes', 'review this PR', 'check my diff', 'review staged changes', or 'pre-merge review'.
    0
    installs
11. ▌
    Error Audit · arndvs bundle

    Use when repeated Claude Code session errors need analysis; scans session transcripts for errors, clusters by root cause, and suggests remediations.
    0
    installs
12. ▌
    Stress Test · arndvs

    Invoke to run the adversarial stress test protocol against ctrl+shft rule compliance. Guides a human reviewer through systematic attempts to break rule boundaries — the same methodology a skeptical senior engineer would use before trusting the system in production.
    0
    installs
13. ▌
    Write A Prd · arndvs

    Write a Product Requirements Document from a rough idea. Use when asked to 'write a PRD', 'create a PRD', 'plan a feature', or when starting a new feature that needs scoping.
    0
    installs
14. ▌
    Agent Assets · arndvs bundle

    Audit the agentic infrastructure committed to a repo — reusable commands, autonomous workflows, vendored documentation, and tool or MCP configuration — and propose what to add, consolidate, or retire. Use when the same prompt is being retyped across sessions, when agent workflows exist but nobody can tell whether they ran or what they did, when orientation files have gone stale or contradict the code, when agents repeatedly fetch the same external docs, or when planning to move work from interactive prompting to scheduled autonomous runs. Also use for requests like "what should be a slash command", "review our .claude directory", "why do our agent workflows keep silently failing", or "audit our AGENTS.md".
    0
    installs
15. ▌
    Plan Archive · arndvs bundle

    Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
    0
    installs
16. ▌
    Pr Preflight · arndvs

    Exhaustive pre-PR audit that front-runs code review tools by catching the same issues Copilot/reviewers find iteratively, across any stack.
    0
    installs
17. ▌
    Press1 Check · arndvs bundle

    Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
    0
    installs
18. ▌
    Repo Hygiene · arndvs bundle

    Drives a long-running, incremental refactor of a messy codebase toward reusable layouts, extracted components, and clean structure. Use whenever the task involves auditing a repo for structural debt, planning the next step of a multi-week refactor, or generating a single well-scoped backlog issue for automated/nightly refactor runs. Also use it when asked to clean up huge monolithic pages, extract layouts or components, migrate page CSS to Tailwind, set up a repeating refactor workflow, or 'improve repo hygiene'. Stack-aware: dispatches to Astro, static-HTML, Worker-TS, or Python audits automatically. Trigger even if the user only says 'what should I clean up next' about a project.
    0
    installs
19. ▌
    Logging Audit · arndvs bundle

    Audit code for logging and observability quality, retrofit code onto whatever logger a repo already uses, and diagnose why a failed run left no usable evidence. Use this whenever reviewing a diff or PR for log quality, cleaning up or standardising logging in a module, judging whether error handling would actually be diagnosable in production, deciding what a catch block should do, or running a postmortem on a job or agent run that failed without explaining itself. Works in any language and any repo. Trigger it for requests like "review the logging here", "why was this run impossible to debug", "is this catch block okay", "make this failure easier to trace", or any investigation of a job that died silently — even when the user never says the word "logging".
    0
    installs
20. ▌
    Prd To Issues · arndvs

    Break a PRD into independently grabbable GitHub issues with dependency relationships. Use when asked to 'break this PRD into issues', 'create issues from PRD', 'plan the work', 'create a kanban', or after writing a PRD to prepare work for execution.
    0
    installs
21. ▌
    Session Close · arndvs

    Pre-flight checklist that runs quality gates before ending a coding session.
    0
    installs
22. ▌
    Atomic Commits · arndvs

    Atomic commits on a feature branch with conventional messages — Commit mode for checkpoints, Ship mode for PR. Use when committing, checkpointing, shipping, pushing, or creating a PR.
    0
    installs
23. ▌
    Codebase Audit · arndvs

    Ruthless codebase audit reporting only real problems. Use when asked to 'audit', 'code audit', 'codebase audit', 'review code', 'find bugs', or 'code review'.
    0
    installs
24. ▌
    Grill With Docs · arndvs bundle

    Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
    0
    installs
25. ▌
    Visual Feedback · arndvs

    Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
    0
    installs
26. ▌
    Compliance Audit · arndvs

    Auto-invoke after any do-work, tdd, systematic-debugging, or review-pr-copilot task completes to review the diff against active rules and skills, flag violations, update the skill if a gap is found, and close the loop between 'rule was loaded' and 'rule was followed'.
    0
    installs
27. ▌
    Skill Scaffolder · arndvs bundle

    Meta-skill for creating new agent skills that involve multi-step automation, browser navigation, state tracking, evidence capture, and both local (VS Code Insiders) and VPS (Playwright) execution. Use when the user wants to 'create a skill', 'build a new skill', 'scaffold a skill', 'make a skill for X', or describes a multi-step agentic workflow they want to automate.
    0
    installs
28. ▌
    Agent Testability · arndvs bundle

    Audit whether a codebase gives a coding agent a reliable way to verify its own work, and propose fixes. Use whenever an agent reports success but the change is broken, when tests exist but don't catch regressions, when the feedback loop is too slow or too noisy for an agent to use, when test failures don't say what broke, or when someone asks how to make a repo safe for autonomous or unattended agent runs. Also use for requests like "why does it keep saying it's done when it isn't", "review our test setup for agents", "what should agents run before opening a PR", or planning a testing strategy where the consumer is an agent rather than a human.
    0
    installs
29. ▌
    Performance Audit · arndvs

    Deep system and codebase performance audit — memory leaks, process bloat, network latency, and runtime profiling. Use when asked to 'performance audit', 'why is everything slow', 'find memory leaks', 'check system health', 'diagnose slowness', or 'perf check'.
    0
    installs
30. ▌
    Review Pr Copilot · arndvs

    Address GitHub Copilot review comments on the active PR by triaging into confidence tiers, fixing in atomic commits, resolving threads, and re-requesting review.
    0
    installs
31. ▌
    Agent Navigability · arndvs bundle

    Audit a codebase for how easily a coding agent can navigate it, and propose structural fixes. Use this whenever an agent keeps re-exploring the same code, burns context finding where things live, edits the wrong file, or misses call sites it should have found; when reviewing structure, naming, module boundaries, or type usage for legibility rather than correctness; when onboarding cost is high for agents or new engineers; or when someone asks why agent runs on this repo are slow, expensive, or unreliable. Also use for requests like "restructure this for agents", "why does it keep missing files", "review our naming", or planning a refactor whose goal is comprehension rather than behaviour. Includes a migration mode for repo-wide restructuring such as separating client from server, splitting a monolith, or changing the top-level layout, which produces a phased plan rather than a findings list.
    0
    installs
32. ▌
    NPM Security Audit · arndvs

    Layered security audit on npm/pnpm/yarn projects before installing or running. Use to vet a GitHub repo, npm package, or local project before npm install/start/npx.
    0
    installs
33. ▌
    Halbert Copy Editor · arndvs

    Edit and punch up sales copy, marketing emails, landing pages, ads, and any persuasive writing using the Halbert Copywriting Method.
    0
    installs
34. ▌
    Sketch The Solution · arndvs bundle

    7-phase UX design process from user stories to tested interfaces. Use when asked to 'sketch the solution', 'design UX', 'UX process', 'product design process', or when going from idea to interface design.
    0
    installs
35. ▌
    Improve Architecture · arndvs

    Explore the codebase for architectural improvements using deep module analysis. Use when asked to 'improve architecture', 'improve codebase', 'find shallow modules', 'refactor architecture', or for periodic codebase health checks.
    0
    installs
36. ▌
    Systematic Debugging · arndvs bundle

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
    0
    installs
37. ▌
    Sanity Best Practices · arndvs bundle

    Sanity development best practices — schemas, GROQ, TypeGen, Visual Editing, Functions, Blueprints, and framework integrations. Use when working with Sanity content, schemas, queries, or Studio.
    0
    installs
38. ▌
    Agent Session Friction · arndvs bundle

    Analyse a completed agent session transcript for evidence that the codebase made the work harder than it needed to be, and record those observations for later consolidation. Use at the end of an agent run, when reviewing a transcript to find what slowed an agent down, when deciding which repo problems are actually costing something, or when someone asks why a run took so many turns or burned so much context. Also use for requests like "audit this session", "what friction did this run hit", "post-run review", or when building automation that collects friction evidence across many runs. Produces observations with measured cost, not issues — publishing is a separate consolidation step.
    0
    installs
39. ▌
    Data Object Conventions · arndvs bundle

    Enforce consistent structure, formatting, and placement for static data objects (catalogs, config, content, lookup tables, enums-as-data) in TypeScript/JavaScript codebases. Use whenever creating, editing, refactoring, or reviewing a data file or data object — including extracting data out of logic files, splitting a monolithic file, deciding where data should live, or formatting a data array. Triggers on phrases like 'data file', 'data object', 'catalog', 'lookup table', 'extract the data', 'split this file', 'format this data', 'where should this data live', 'this data is ugly'. Do NOT use for runtime state, API responses, or database rows — those are data-in-motion, not static data.
    0
    installs
40. ▌
    Frontend Component Style · arndvs

    Frontend component file structure, naming, and layer separation for new or refactored components.
    0
    installs