all publishers

amsborse

@amsborse source repo

44 published skills

  1. ▌
    Night Consistency · amsborse
    Consistency loop. Select one naming, error-handling, component or theme-token inconsistency, align a bounded set with an established repository pattern, and retain it only when checks show no regression. Use for "night-consistency", "night consistency" or as /night consistency.
    0 installs
  2. ▌
    Night Performance · amsborse
    Performance loop. Measure one real bottleneck with repeated baseline and candidate runs, make one bounded optimisation, and retain it only when the measured gain exceeds noise and behaviour stays stable. Use for "night-performance", "night performance" or as /night performance.
    0 installs
  3. ▌
    Night Dependencies · amsborse
    Dependency loop. Review advisories and update one package or lockstep group with the project package manager, favour patch and minor releases, and keep only a tested change with a consistent lockfile. Use for "night-dependencies", "night dependencies" or as /night dependencies.
    0 installs
  4. ▌
    Working Agreements · amsborse
    The owner's standing rules for any coding agent, learned from their repeated instructions and corrections across coding agents. Use at the start of any coding, debugging, UI or automation task in the owner's repositories; before reporting work as done or fixed; before any commit, push, merge, deploy or paid model call; when touching secrets, git state or another agent's work; during long autonomous or overnight runs; and for any UI, visual design or animation change. A repository's AGENTS.md and the current task's explicit instructions take precedence.
    0 installs
  5. ▌
    Night Accessibility · amsborse
    Accessibility loop. Repair one evidenced interface barrier and retain it only when violation counts fall, keyboard paths work and no new barriers appear. Use for "night-accessibility", "night accessibility" or as /night accessibility.
    0 installs
  6. ▌
    Night Evolve Skills · amsborse
    Skill-evolution loop. Improve one catalog skill from recorded failures and repeated corrections, validate the edit, and reserve changes to the active loop or engine for human application. Use for "night-evolve-skills", "night evolve skills" or as /night evolve-skills.
    0 installs
  7. ▌
    Understand Code · amsborse
    Understand and explain a codebase or one area of it — architecture, entry points, data flow, dependencies, conventions and risky spots — with file:line evidence, as a short map or a diagram. Use for "understand the architecture of this repository", "how does X work", "explain this codebase", onboarding, or before changing unfamiliar code.
    0 installs
  8. ▌
    Add Interactions · amsborse
    Add hover, press, drag and pointer interactions that fit the product (magnetic hover, cursor light, tilt, springs, drag) with keyboard parity, touch fallbacks and reduced motion, browser-verified. Use for "add hover interactions" or "micro-interactions".
    0 installs
  9. ▌
    Automate Browser · amsborse
    Automate a browser workflow — navigate, fill forms, click through flows, extract page data, take screenshots, or turn a repeated manual task into a reusable script — with the cheapest reliable browser tool available and explicit confirmation before anything outward-facing (submitting, purchasing, posting, sending). Use for "automate this browser workflow", "fill this form", "scrape this page", "click through this flow" or "make a script for this web task".
    0 installs
  10. ▌
    Night Bug Hunter · amsborse
    Bug-hunting loop. Start from a red baseline, reproduce one failure, add a failing regression test and repair its root cause, keeping the fix only when the original failure and relevant checks pass. Use for "night-bug-hunter", "night bug hunter" or as /night bugs.
    0 installs
  11. ▌
    Production Ready · amsborse
    Never deploy, publish or change production config unless the user asked for it in this task.
    0 installs
  12. ▌
    Replicate Design · amsborse
    Reproduce how a reference feels and behaves, not its property. Never copy its images, fonts,
    0 installs
  13. ▌
    Coordinate Agents · amsborse bundle
    Split work across agents — delegate an isolated implementation to OpenAI Codex through codex-bridge in its own git worktree, run independent parts in parallel subagents, then review and integrate the results yourself. Includes the former /codex-frontend workflow. Use for "use Codex for this", "delegate to Codex", "split this work", "run agents in parallel" or "orchestrate agents".
    0 installs
  14. ▌
    Security Audit · amsborse
    Audit a codebase or change for security problems — secrets, authentication and authorization, injection, XSS/CSRF/SSRF, unsafe deserialization, dependency CVEs, risky install scripts, permissions and data exposure — with a threat model sized to the system, concrete exploit scenarios, and fixes. Also reviews third-party skills, plugins and MCP servers before adoption. Read-only unless fixes are asked for. Use for "security audit", "security review", "threat model", "is this safe" or "check for secrets".
    0 installs
  15. ▌
    Build Animation · amsborse bundle
    Motion rules are in the UI taste section of ~/agent-skills/working-agreements/AGENTS.md: one
    0 installs
  16. ▌
    Improve Visuals · amsborse bundle
    Make an existing UI look better in rounds, judged blind on real screenshots, not on speed. Use for "improve the visuals" or "make it look better".
    0 installs
  17. ▌
    Test Everything · amsborse bundle
    Plan, write and run tests across the stack — unit, integration, end-to-end and visual — find the gaps that matter, fix flaky tests at the cause, and report real results. Use for "test everything", "add tests", "improve test coverage", "set up e2e tests", a test strategy, or when a change needs proof beyond reading the code.
    0 installs
  18. ▌
    Night Redteam · amsborse
    Red-team loop. Prove one exploitable trust-boundary failure only with a local failing test, then repair its root cause or record an owner decision when no safe fix fits. Use for "night-redteam", "night redteam" or as /night redteam.
    0 installs
  19. ▌
    Create Visuals · amsborse
    One signature visual per product acts as its brand mark: it belongs to the page, blended in
    0 installs
  20. ▌
    Night Refactor · amsborse
    Refactoring loop. Characterise existing behaviour before simplifying one bounded area, preserve the public API, and keep the change only when tests and review show equivalent behaviour with less complexity. Use for "night-refactor", "night refactor" or as /night refactor.
    0 installs
  21. ▌
    Night Research · amsborse
    Research loop. Investigate one repository question with primary sources and code evidence, then return a cited markdown report with confidence levels and unknowns, without changing any files in the worktree. Use for "night-research", "night research" or as /night research.
    0 installs
  22. ▌
    Review Changes · amsborse bundle
    A report the owner can read without opening the code: the interface as pictures, everything else
    0 installs
  23. ▌
    Run Autonomous · amsborse
    Run a long or multi-step task autonomously — overnight, while the user is away, or until a list of milestones is done — with an isolated branch or worktree, a ledger of progress and decisions, bounded retries, and an evidence-backed report. Includes the nightly-evolution routine (one draft PR of improvements per night). Never pushes, merges or deploys unless asked. Use for "run this task autonomously overnight", "keep going until done", "work on this while I sleep" or "run nightly evolution".
    0 installs
  24. ▌
    Audit Design · amsborse bundle
    An audit reports; it does not fix. Change code only when the user asks for fixes, then hand
    0 installs
  25. ▌
    Night Visual · amsborse
    Visual loop. Improve one evidenced interface issue, compare real screenshots in both themes and configured viewports, and retain the change only when visual review and runtime checks support it. Use for "night-visual", "night visual" or as /night visual.
    0 installs
  26. ▌
    Build Feature · amsborse bundle
    Build a feature end to end — ground it in the code, write a short brief, implement, test, verify on the real target and review. Scales from a small change (just do it and verify) to a large feature (spec first, worktree, parallel workers). Use when asked to build, add or implement a feature, "build this end to end", or "write a spec/brief" for one (the former /spec).
    0 installs
  27. ▌
    Manage Skills · amsborse
    Manage this skill catalog — find which skill fits a request, create or update a skill, vet and adopt a third-party skill, reinstall or repair skill discovery for any agent, and learn new rules from past agent conversations (history-learning). Use for "which skill should I use", "add a skill", "update my skills", "install skills", "learn from my history" or when a skill seems missing or broken.
    0 installs
  28. ▌
    Night Improve · amsborse
    Improvement loop. Rank small repository improvements by evidence, make the best bounded change, and keep it only when checks prove the intended benefit without regressions. Use for "night-improve", "night improve" or as /night improve.
    0 installs
  29. ▌
    Experience · amsborse
    One entry point to make a web product look, feel and perform better. Audits first, then runs the fewest creative skills that fit. Use for "/experience" or "take this site to the next level".
    0 installs
  30. ▌
    Night Docs · amsborse
    Documentation loop. Find one mismatch between repository instructions and actual code, correct it with precise examples, and retain the edit only when the documented commands and claims are verified locally. Use for "night-docs", "night docs" or as /night docs.
    0 installs
  31. ▌
    Night Ideas · amsborse
    Idea loop. Rank product and engineering opportunities from repository evidence with explicit priority scores, returning actionable proposals and follow-ups without writing files. Use for "night-ideas", "night ideas" or as /night ideas.
    0 installs
  32. ▌
    Night Tests · amsborse
    Test-coverage loop. Each iteration finds the riskiest untested behavior, adds one focused test in the project's own style, proves it would catch a break, and keeps it only if the suite stays green. Use for "night-tests", "add tests overnight", "grow coverage in a loop" or as /night tests.
    0 installs
  33. ▌
    Review Code · amsborse
    Review a diff, branch, commit or PR for real bugs, performance problems, needless complexity and missing tests, and verify every finding before reporting it. By default the review is an independent read-only pass by OpenAI Codex through codex-bridge (the former /codex-review); without the bridge it is a careful self-review. Use for "review this", "code review", "second opinion", "have Codex check it", or before calling a large change done.
    0 installs
  34. ▌
    Research · amsborse
    Never invent sources, numbers or quotes. Unknown stays unknown.
    0 installs
  35. ▌
    History Learning · amsborse bundle
    Learn durable preferences, corrections, decisions and working patterns from historical coding-agent conversations (Claude Code, Codex, Cursor, OpenCode, Antigravity, Kiro, Qwen) and turn them into reviewed, evidence-backed skill updates. Use when asked to learn from past conversations or chat history, mine repeated corrections or preferences, update skills from experience, run incremental history learning, or audit what has been learned. Read-only over history, consent-gated per source, redacts before any model sees text, and never publishes or overwrites skills on its own.
    0 installs
  36. ▌
    Revamp UI · amsborse bundle
    The bar is the UI taste section of ~/agent-skills/working-agreements/AGENTS.md, with details and
    0 installs
  37. ▌
    Verify · amsborse
    Verify a change where the user actually looks at it (local browser, Vercel/production URL, LG TV, Windows desktop app, Chrome extension) and report pass/fail with real evidence. Use when the user runs /verify, says something is "still broken" / "I still see the old one", or before claiming a UI or runtime fix is done.
    0 installs
  38. ▌
    Fix Bug · amsborse
    Find and fix a bug — reproduce it on the real target, find the root cause, write a failing regression test, fix, and confirm the fix where the user saw the bug. Use for errors, crashes, failing tests or CI, wrong behavior, "this is broken", "still broken" or "I still see the old one".
    0 installs
  39. ▌
    Improve · amsborse
    Audit a project or area for improvements, rank them, implement the safe ones and verify them in one pass, then list the rest as numbered options. Also covers behavior-preserving refactors and measured performance work. Use when the user runs /improve [area], asks "what can be improved" (and would otherwise follow up with "implement all"), or asks to refactor, clean up or speed something up.
    0 installs
  40. ▌
    Build 3d · amsborse
    3D is earned, never a default. First ask whether a flat technique does the job
    0 installs
  41. ▌
    Build UI · amsborse
    New UI should look like it was always part of the product. Extend what exists: the project's
    0 installs
  42. ▌
    Night QA · amsborse
    User-flow QA loop. Exercise one main journey end to end, capture reproducible breaks, and add one regression-backed repair or a precise bug-hunter follow-up, with runtime evidence for every claim. Use for "night-qa", "night qa" or as /night qa.
    0 installs
  43. ▌
    Ship · amsborse
    Ship finished work end to end once the user asks for it — run the checks, compare failures with a baseline on main, merge, push, deploy and health-check when the repo has a deploy step, then clean up this session's branches, worktrees and servers and report the commit. Use for "ship it", "merge and push", "merge, push and deploy", "merge to main and clean up" or "push everything and delete the branches". Not for deciding whether something is ready (production-ready) or for unasked releases.
    0 installs
  44. ▌
    Night · amsborse bundle
    Run autonomous, verified improvement loops on a repository overnight or while away. It plans by priority, works on an isolated run branch, delegates each iteration to an agent, verifies and keeps or reverts every change, survives crashes through a watchdog, and writes an evidence-only morning report. Never pushes, merges or deploys. Use for "/night", "/night auto", "/night tests", "run loops overnight", "night status", "night report" or "stop the night run".
    0 installs