andysolomon
- 36 skills
- 0 followers
- 4 hours ago last updated
- ▌ Shell · andysolomonRuns the rest of a /shell request as a literal shell command. Use only when the user explicitly invokes /shell and wants the following text executed directly in the terminal.
- ▌ Create Rule · andysolomonCreate Cursor rules for persistent AI guidance. Use when you want to create a rule, add coding standards, set up project conventions, configure file-specific patterns, create RULE.md files, or asks about .cursor/rules/ or AGENTS.md.
- ▌ Create Skill · andysolomonGuides users through creating effective Agent Skills for Cursor. Use when you want to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.
- ▌ Update Cursor Settings · andysolomonModify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
- ▌ Creating User Stories · andysolomonCreates development plans with user stories and GitHub issues. Use when asked to plan features, create stories, write issues, build a backlog, or create a development roadmap.
- ▌ Ideabrowser Openclaw Flow · andysolomon bundleExtract startup idea details from IdeaBrowser and produce deterministic scaffold specs for implementation plans and progress tracking. Playwright CLI is primary; OpenClaw is fallback.
- ▌ Implementation Plan Progress · andysolomon bundleCreate or update highly specific implementation plans and aligned progress trackers for software projects. Use when a user asks for an implementation plan, roadmap, phased delivery plan, gap analysis against an idea/spec, or asks to create/update `progress.txt` with actionable checklist items mapped to milestones.
- ▌ Project Deploy Portfolio Sync · andysolomon bundleDeploy a project to Vercel and add/update its case-study presence on andrewsolomon.dev (project page plus homepage card), then redeploy the portfolio site and verify links.
- ▌ Create Subagent · andysolomonCreate custom subagents for specialized AI tasks. Use when you want to create a new type of subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants with custom prompts.
- ▌ Migrate To Skills · andysolomonConvert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.
- ▌ Skill Creator · andysolomon bundleGuide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
- ▌ Andrew Mode · andysolomonAndrew's working conventions for agents. Use for /andrew-mode, "andrew mode", or a request to work in his style.
- ▌ Arc Bug Fixer · andysolomonPicks up a bug ticket filed by arc-bug-finder (in GitHub Issues, GitLab, or Linear), critically reviews and re-validates it, then implements, verifies, and ships the fix — branch, conventional commit, PR, and ticket update. Reviewing is the core competency: it re-reproduces the defect, confirms the cited root cause still exists, and chooses the best fix rather than trusting the ticket blindly. Delegates plan formatting to arc-planning-work, commit/PR mechanics to arc-conventional-commits / arc-git-pr-check. TRIGGER when: user asks to fix/resolve/implement a filed bug, points at a bug ticket or issue number, says "fix this bug", "resolve W-######", or "work the bug backlog". DO NOT TRIGGER when: user is reporting a NEW bug or asking "why is this happening" (use arc-bug-finder to research + file first), or planning greenfield features (use arc-defining-work).
- ▌ Arc Bug Finder · andysolomonInvestigates a reported bug (often from a screenshot) through exhaustive repo search and online research, isolates the root cause, recommends the best possible fix, then files it as a bug in the tracker the codebase already uses (GitHub Issues, GitLab, or Linear). Delegates story formatting to arc-creating-user-stories and plan formatting to arc-planning-work. TRIGGER when: user reports a bug, shares a screenshot of broken behavior, asks "why is this happening", or asks to file/triage/research a defect. DO NOT TRIGGER when: user asks to implement a fix (use arc-bug-fixer), or to plan greenfield features (use arc-defining-work).
- ▌ Arc Work Issue · andysolomon bundleWork an open GitHub issue in a new git worktree, then ship it — merge the PR (default), enable auto-merge, or leave the PR open for review. Invoke with `#14` or `W-000014`, optionally `--ship merge|auto|pr`.
- ▌ Arc Gitlab Glab · andysolomon bundleGitLab delivery via the glab CLI and GitLab CI/CD YAML. Use when creating/protecting GitLab projects, opening or merging MRs, setting masked/protected CI variables, scheduling pipelines, or authoring/debugging .gitlab-ci.yml — including reusable pipeline templates (hidden jobs + extends + include), rules-based conditional execution, dotenv artifact passing, manual release gates, scheduled drift/backup jobs, and Kaniko image builds. Triggers on glab, .gitlab-ci.yml, GitLab CI, GitLab pipeline, protected branch, CI variable, GitLab schedule, merge request, or "set up GitLab CI". Encodes hard-won gotchas (masked-variable charset, protected-vars-vs-MR-pipelines, protected-ref hotfix gating, YAML-anchor script splice).
- ▌ Arc Git Pr Check · andysolomon bundleIdempotent git workflow that commits if needed, pushes if needed, creates a PR if missing, and ships it per --ship mode (enable squash auto-merge, squash-merge now, or leave the PR open for review). With --update-main, it can fast-forward the local default branch and safely clean the current linked worktree after a confirmed merge. If changes exist on the default branch, it stashes changes, creates a semver feature branch, then restores changes before committing. Other skills (arc-work-issue, arc-parallel-implement) delegate PR mechanics here.
- ▌ Arc Defining Work · andysolomon bundleDestination router for new work-item creation across GitHub Issues, Linear, or Agile Accelerator. Use when asked to create stories, build a backlog, define work from codebase analysis, or convert requirements into tracked work items and the destination tracker is not yet fixed. Do not use for implementation planning of existing work.
- ▌ Arc Planning Work · andysolomon bundleImplementation planning for existing tracked work items. Use when asked to plan an existing GitHub issue, Agile Accelerator story, or PRD before coding begins. Produces ordered tasks, file-level changes, test strategy, acceptance-criteria mapping, and synchronized docs/<ID>-IMPLEMENTATION_PLAN.md plus docs/<ID>-progress.txt artifacts. Do not use to create new user-story backlogs.
- ▌ Arc Prd To Issues · andysolomon bundlePRD-to-GitHub-issues slicing with tracer-bullet vertical slices. Use when converting a PRD into independently grabbable GitHub issues, reviewing slice granularity, or creating implementation tickets from a PRD. Do not use for implementation plans of existing issues.
- ▌ Arc Sf JWT Bearer · andysolomonGenerates RSA keypairs and tests JWT bearer token flow against Salesforce orgs. Use when setting up server-to-server auth, creating Connected Apps with JWT, or troubleshooting JWT bearer flow errors.
- ▌ Arc System Design · andysolomon bundleSystem-design learning coach. Teaches system design by guiding the user through designing and then building real systems (e.g. a todo app, a Twitter-style feed, a video streaming service) rung by rung. Use when the user wants to learn or practice system design, scope/design a system, continue a guided build ("next rung", "done", "continue where we left off"), have their code reviewed as part of the build, or rehearse interview narration. Guide mode — the user writes all concept-bearing code; the agent explains concepts, assigns small tasks, runs and verifies the result with real requests, reviews the code, and teaches transferable lessons.
- ▌ Arc Creating Evals · andysolomon bundleAuthors an arc-skill-eval test suite for an existing skill. Produces `evals/evals.json` in the target skill's directory plus any `evals/files/` fixtures the cases need. Use whenever the user says "write evals for this skill", "add eval coverage", "create evals.json for this skill", "scaffold evals for this skill", or "make this skill testable". Follows the Anthropic skill-eval methodology (evals/evals.json + assertion grading). Produces output next to the target skill's SKILL.md so the eval travels with the skill.
- ▌ Arc Creating Skill · andysolomon bundleCreates or revises agent skills in agentskills.io `SKILL.md` format. Use when the user asks to create a new skill, turn notes into a skill, improve a skill, split/consolidate skills, apply skill-writing best practices, or make a skill predictable and concise.
- ▌ Arc Pr Review Loop · andysolomon bundleReview a PR against its plan, post actionable PR comments, have a coding agent address them, and repeat until approved or a round limit is hit. Invoke with a PR number/URL, e.g. `/arc-pr-review-loop 27`.
- ▌ Arc Contract Review · andysolomon bundleContract review for legal agreements, NDAs, employment terms, SaaS/MSA terms, payment agreements, finder/broker agreements, and M&A documents. Use when analyzing contract risk, extracting key terms, suggesting redlines, or preparing negotiation priorities. Informational only, not legal advice.
- ▌ Arc Webgl Performance · andysolomon bundleProfile and improve performance in browser applications with Three.js, WebGL, Canvas, or other continuously rendered 3D scenes. Use when adding or debugging scene construction, shader/material warmup, procedural generation, texture baking, orbit or camera transitions, animation loops, visibility and pause behavior, or performance budgets and CI benchmarks.
- ▌ Arc Parallel Implement · andysolomon bundleImplements multiple planned user stories in parallel with isolated worktrees, using Arc Pi native subagents when available or the non-Pi external orchestrator fallback. Each accepted story gets its own branch, commit, and PR.
- ▌ Arc Conventional Commits · andysolomon bundleSet up Conventional Commits with semantic-release for automated semantic versioning. Use this skill whenever the user mentions conventional commits, semantic versioning, semver, release automation, auto version bumping, changelog generation, commit message standards, semantic-release, or wants to configure automated releases. Also trigger when the user asks about commit message formats like "feat:", "fix:", or "BREAKING CHANGE", or wants to replace an existing versioning system (standard-version, changesets, lerna, release-please) with semantic-release. Even if the user just says "set up versioning" or "add release automation", this skill applies.
- ▌ Arc Linear Issue Creator · andysolomonBulk-creates Linear issues with verifiable checklist acceptance criteria, W-number sequencing, label taxonomy, and dependency tracking. Integrates with arc-creating-user-stories and arc-defining-work story format. TRIGGER when: user wants to create issues in Linear, bulk-create stories, push user stories to Linear, or populate a Linear project backlog. DO NOT TRIGGER when: managing existing Linear issues (triage, sprint planning, status updates), creating GitHub Issues, or creating Agile Accelerator records.
- ▌ Arc Creating User Stories · andysolomon bundleUser-story backlog creation for GitHub Issues using job stories with verifiable checklist acceptance criteria. Use when asked to create development stories, write GitHub issues from a plan, build a feature backlog, or turn feature ideas into tracked user stories. Do not use for implementation planning after issues already exist.
- ▌ Arc Ideabrowser Openclaw Flow · andysolomon bundleIdeaBrowser extraction into scaffold-ready specs. Use when crawling an IdeaBrowser idea page, extracting startup idea details, or producing a deterministic scaffold spec for implementation planning/progress tracking. Playwright CLI is primary; OpenClaw is fallback.
- ▌ Arc Implementation Plan Progress · andysolomon bundleImplementation-plan/progress tracker creation for software projects. Use when a user asks for an implementation plan, phased roadmap, gap analysis against a spec, or synchronized `IMPLEMENTATION_PLAN.md` and `progress.txt` execution tracker. Do not use for creating GitHub user-story backlogs.
- ▌ Arc Project Deploy Portfolio Sync · andysolomon bundleVercel deploy plus andrewsolomon.dev portfolio sync. Use when a finished project should be deployed, added or updated as a portfolio case study, linked from the homepage, and verified end-to-end. Do not use for generic Vercel troubleshooting or portfolio copywriting alone.
- ▌ Arc Demo Linear Export · andysolomon bundleCreates Linear issues from a local planning document. Use when the user asks to turn a plan into Linear issues, bulk-create Linear work items, or sync roadmap tasks into Linear. Requires a Linear API token for live issue creation.
- ▌ Arc Demo File Writer · andysolomon bundleCreates a short project summary file from local notes. Use when the user asks to summarize notes into notes/summary.md, create a project summary, or turn raw notes into a concise markdown artifact. Do not use for general prose editing or unrelated documentation tasks.