all publishers

joshuadavidthomas

@joshuadavidthomas source repo

34 published skills

  1. ▌
    Using Superpowers · joshuadavidthomas bundle
    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
    63 repo stars
  2. ▌
    Codspeed Profiling · joshuadavidthomas
    Use when diagnosing CodSpeed benchmark regressions, profiling with valgrind-codspeed/callgrind, comparing instruction counts between branches, or reading callgrind_annotate output. Also use when a CodSpeed PR check shows performance regression and you need to find the cause. Covers: just profile, callgrind Ir/Dr/Dw counts, flat vs tree annotation, branch comparison methodology.
    63 repo stars
  3. ▌
    Subagent Driven Development · joshuadavidthomas bundle
    Use when executing implementation plans with independent tasks in the current session
    63 repo stars
  4. ▌
    Finishing A Development Branch · joshuadavidthomas
    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
    63 repo stars
  5. ▌
    Djls Salsa · joshuadavidthomas
    Use when editing Salsa inputs, tracked functions, database traits, setters, SemanticDb, crate::Db, invalidation behavior, or incremental computation in django-language-server. Handles project-specific Salsa conventions and required impl updates.
    63 repo stars
  6. ▌
    Djls Testing · joshuadavidthomas
    Use when running tests, fixing failing tests, updating snapshots, syncing corpus data, validating before push, or working with Django matrix testing in django-language-server. Handles cargo, just, nox, insta, corpus, clippy, fmt, and lint commands.
    63 repo stars
  7. ▌
    Djls Ruff Ast · joshuadavidthomas
    Use when editing djls-extraction or Rust code that consumes Ruff Python AST APIs, including parse_module, parameters, boxed expressions, f-strings, or exception handlers. Handles known Ruff AST shape gotchas in django-language-server.
    63 repo stars
  8. ▌
    Djls Changelog · joshuadavidthomas
    Use when adding release notes, changelog entries, user-facing changes, internal changelog notes, or preparing a PR/release for django-language-server. Handles Keep a Changelog formatting and entry style.
    63 repo stars
  9. ▌
    Djls Resolver Corpus · joshuadavidthomas
    Maintain the ported ty resolver test corpus in crates/djls-project/tests/resolve.rs. Use when bumping the ruff git pin in the workspace Cargo.toml or when adding/reviewing module-resolution tests.
    63 repo stars
  10. ▌
    Djls Domain Conventions · joshuadavidthomas
    Use when editing Django template parser tags, validation errors, diagnostics, environment scanning, inspector data, Python environment inventory, or DJLS domain model code. Handles project-specific semantic and parser conventions.
    63 repo stars
  11. ▌
    Djls Workspace Conventions · joshuadavidthomas
    Use when adding or editing crates, Cargo.toml files, workspace dependencies, crate manifests, lints, versions, or project structure in django-language-server. Handles Rust workspace layout, dependency grouping, and new crate setup.
    63 repo stars
  12. ▌
    Improving Prompts · joshuadavidthomas bundle
    Use when optimizing CLAUDE.md, AGENTS.md, custom commands, or skill files — diagnose the concrete failure first, then apply current documented Anthropic best practices (explicit instructions, context/motivation, examples, output and verbosity control, thinking/effort, CLAUDE.md size and skill-description rules) instead of inventing improvements. Triggers when a prompt isn't followed, a skill won't activate, CLAUDE.md is too long or ignored, or migrating prompts to current Claude models.
    63 repo stars
  13. ▌
    Strategic Roadmap · joshuadavidthomas bundle
    Use when a user asks “what should I work on in this repo?”, “what’s worth doing next?”, repo audit, tech-debt priorities, architecture priorities, old-plan reconciliation, or repo-grounded opportunity discovery. Produces .agents/ROADMAP.md with generated opportunities, user-seeded ideas, Now/Next/Later sequencing, rejected/not-now items, and next-artifact recommendations. Not for standard product/release roadmaps; if multiple repos are requested, create one roadmap per repo.
    63 repo stars
  14. ▌
    Writing CLI Skills · joshuadavidthomas bundle
    Use when authoring an agent skill that wraps a command-line tool — covers hands-on tool exploration, required vs. recommended sections, installation/usage structure, trigger-rich descriptions, task-grouped commands, progressive disclosure, and a pre-publish checklist. Triggers for CLI / command-line / terminal / shell-command tools and binary wrappers; for review, run the Checklist section.
    63 repo stars
  15. ▌
    Writing Error Messages · joshuadavidthomas bundle
    Use when writing, reviewing, or rewriting user-facing error messages, validation messages, form errors, empty/error states, auth errors, failure notifications, retry/support copy, CLI errors, or API errors humans will read. Helps make errors specific, actionable, non-blaming, accessible, and safe without leaking sensitive details.
    63 repo stars
  16. ▌
    Roadmap To Improve Plans · joshuadavidthomas bundle
    Use when turning a roadmap, repo priorities, architecture priorities, chosen opportunities, accepted feature outlines/plans, or “roadmap to plans” request into grouped improvement plan batches for future executors. Writes README.md indexes, 001-*.md/NNN-style plans, optional memo-*.md files, verification gates, drift checks, STOP conditions, rejected approaches, and executor handoff notes.
    63 repo stars
  17. ▌
    Feature Planning Artifacts · joshuadavidthomas bundle
    Use when creating or iterating staged planning artifacts for a complex feature: design discussion, structure outline, final executor plan, or supporting research/research questions. Also use when designing before coding, breaking work into vertical slices, or deepening a high-value roadmap item, NNN improve plan, architecture candidate, or HumanLayer-style task.
    63 repo stars
  18. ▌
    Frontend Design Principles · joshuadavidthomas bundle
    Use when building or reviewing frontend UI — dashboards, admin panels, landing pages, marketing sites, web apps. Drives domain-specific design decisions (typography, color world, layout, CSS token naming, depth and spacing systems) instead of generic AI defaults; routes to app.md (product/data UIs) or marketing.md (public/creative pages) by context.
    63 repo stars
  19. ▌
    Svelte5 · joshuadavidthomas bundle
    Reviews Svelte components for idiomatic patterns, identifies anti-patterns carried over from React/Vue/Svelte 4, and suggests Svelte 5 refactorings. Use when writing or reviewing Svelte components, asking "is this idiomatic", "Svelte way", doing Svelte 5 migration, or encountering smells like: effect assigns state, prop copied to $state, global store by default, $bindable everywhere, clickable div, createEventDispatcher, export let, on:click, slot-shaped APIs, lifecycle-driven code, imperative DOM wiring, immutable-update ceremony, context value replacement, shadcn-svelte form structure, Field.* components, bits-ui form controls, or component APIs that hide ownership. This is the general-purpose entry point for Svelte component review; delegates to sveltekit for routes/load/actions/server concerns and to focused references for details.
    63 repo stars
  20. ▌
    Writing · joshuadavidthomas bundle
    General prose doctrine for anything a human will read — clear, concrete, free of ready-made phrases. Use when writing or editing documentation, explanations, summaries, commit messages, reports, or any other prose.
    63 repo stars
  21. ▌
    Diataxis · joshuadavidthomas bundle
    Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.
    63 repo stars
  22. ▌
    Sveltekit · joshuadavidthomas bundle
    Mental-model reset for SvelteKit apps. Use when writing or reviewing routes, layouts, load functions, form actions, remote functions, hooks, auth, cookies, endpoints, redirects, errors, SSR, progressive enhancement, or app-level data flow. Triggers on SvelteKit, +page, +layout, +server, +page.server.ts, +layout.server.ts, hooks.server.ts, load, actions, fail(), redirect(), error(), cookies, locals, route groups, protected routes, sessions, form actions, enhance, remote functions, command(), query(), form(), getRequestEvent(), SSR, hydration, and serialization. Use svelte5 for component-level runes, snippets, accessibility, actions, transitions, and component API review.
    63 repo stars
  23. ▌
    Writing Plans · joshuadavidthomas bundle
    Write self-contained implementation plan files that a fresh, possibly weaker executor can run without the author's context — splitting work into PR-sized plans, with verification gates, STOP conditions, and a memo protocol for design forks. Use when asked to write/create a plan, turn a decided design or ticket into plans, or when another skill hands off plan-writing. Not for deciding what to build or executing plans.
    63 repo stars
  24. ▌
    English Please · joshuadavidthomas
    Dude, come on. You write at the density of your own thinking and leave the reader to unpack it. Apply whenever explaining anything to a human — not just end-of-run summaries, every message.
    63 repo stars
  25. ▌
    HTML Artifacts · joshuadavidthomas bundle
    Use when the user asks to create, generate, visualize, or turn material into a standalone HTML artifact, self-contained or single-file .html report, interactive explainer, interactive illustration or visualization, visual walkthrough or handoff, or HTML presentation or slide deck. Handles source-grounded codebase and architecture, feature, PR or diff, implementation recap, incident timeline, option comparison, causal, and data-report explanations. Not for prose-only analysis or reviews, production web apps or dashboards, websites, HTML email, or ordinary frontend/UI implementation.
    63 repo stars
  26. ▌
    Coolify Compose · joshuadavidthomas bundle
    Convert Docker Compose files to Coolify templates. Use when creating Coolify services, converting docker-compose.yml for Coolify deployment, working with SERVICE_URL/SERVICE_PASSWORD magic variables, or troubleshooting Coolify compose errors.
    63 repo stars
  27. ▌
    Skill Authoring · joshuadavidthomas bundle
    Use when authoring, creating, refining, or troubleshooting agent skills — scaffold SKILL.md and frontmatter, write and optimize the trigger description, structure the body with progressive disclosure, validate structure, and test or debug activation. Also when building a new skill from scratch, when a skill won't trigger, loads incorrectly, or the agent ignores it entirely. Use when a skill misbehaved in the current session and needs adjustment based on learnings.
    63 repo stars
  28. ▌
    Coding Standards · joshuadavidthomas bundle
    Use when reviewing code quality, asking whether a refactor or design is good, looking for code smells, or evaluating architecture tradeoffs. Identifies shallow interfaces, invalid state models, unclear boundaries, hidden effects, weak failure contracts, over-mocking, over-abstraction, compatibility glue, and clean-looking code that preserves bad models.
    63 repo stars
  29. ▌
    Grug Brained Dev · joshuadavidthomas
    Use when reviewing PRs, simplifying over-engineered code, judging architecture, or renaming unclear concepts — inline fake helpers, delete meatless ceremony, rename lying names, merge over-split files, reject premature abstraction, say no to speculative config/modes/layers, then end with the smallest safe next change. Triggers when code is too fancy, too abstract, too clever, too many files/helpers/layers, or too well-factored but painful to change. Embody Grug brain: complexity very bad, small words, no consultant speak, no hard pivot to opposite dogma.
    63 repo stars
  30. ▌
    Jj · joshuadavidthomas bundle
    Jujutsu (jj) — the Git-compatible version control system. Activate ONLY when a .jj/ directory is present in the project or when jj/jujutsu is explicitly mentioned. Do NOT activate for plain git repos without .jj/. Use for any VCS operations in jj-managed projects: commit, push, pull, branch, bookmark, rebase, squash, merge, diff, log, status, working copy, change ID, revset, fileset, template, configuration, workspaces.
    63 repo stars
  31. ▌
    Rust · joshuadavidthomas bundle
    Mental-model reset for Rust. Use when writing or reviewing Rust code to shift from "it compiles" to "thinks in Rust." Triggers on Rust code review, "is this idiomatic", borrow-checker errors, API design, domain modeling, ownership, lifetimes, errors, traits, async/Tokio, unsafe, serde, FFI, tests, performance, Cargo structure, .rs files, Cargo.toml, rustc diagnostics, clippy findings, Result/Option, thiserror vs anyhow, newtype, typestate, enum vs trait, dyn Trait, Send/Sync, Pin, Miri, PyO3, napi-rs, cxx, UniFFI, wasm-bindgen, serde attributes, or feature unification.
    63 repo stars
  32. ▌
    Salsa · joshuadavidthomas bundle
    Mental-model reset for Salsa, the incremental computation framework for Rust. Use when building or reviewing Salsa databases, tracked functions, input/ tracked/interned structs, query pipelines, accumulators, cancellation, durability, LSP integration, memory management, cycles, or production Salsa architecture. Triggers on #[salsa::db], #[salsa::input], #[salsa::tracked], #[salsa::interned], #[salsa::accumulator], salsa::Storage, memoization, revisions, backdating, red-green algorithm, WillExecute, DidValidateMemoizedValue, Cancelled, returns(ref), no_eq, lru, cycle_fn, cycle_result, durability, or salsa::Event.
    63 repo stars
  33. ▌
    Improve · joshuadavidthomas bundle
    Survey a codebase as a senior advisor and turn the highest-value findings into implementation plans for other agents to execute — strictly read-only on source code, never implements anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, architecture, migrations, DX), suggest features or roadmap direction, or generate handoff plans for another agent to implement.
    63 repo stars
  34. ▌
    Roadmap · joshuadavidthomas bundle
    Build evidence-backed software/product roadmaps from repo state, tickets, ideas, audit findings, or user goals — prioritize and sequence work across Now/Next/Later, milestones, dependencies, risks, and handoffs. Use when asked for a roadmap, feature roadmap, technical roadmap, release plan, milestone plan, backlog prioritization, sequencing, what to build next, or to turn improve/ideate/brainstorm/design-discussion outputs into an execution sequence. Not for implementing code or writing PR-level plans.
    63 repo stars