css-modern
Use modern CSS features - custom properties, container queries, :has(), @layer, CSS nesting
css-fundamentals
CSS fundamentals - selectors, specificity, box model, positioning, units
gws-gmail-send
Gmail: Send an email.
gws-gmail
Gmail: Send, read, and manage email.
gws-shared
gws CLI: Shared patterns for authentication, global flags, and output formatting.
gws-calendar-insert
Google Calendar: Create a new event.
gws-gmail-reply
Gmail: Reply to a message (handles threading automatically).
gws-calendar
Google Calendar: Manage calendars and events.
gws-gmail-read
Gmail: Read a message and extract its body or headers.
gws-calendar-agenda
Google Calendar: Show upcoming events across all calendars.
complete
Finish work and reset local environment for next task. Use this when the user is done with a feature branch, wants to clean up after a merged PR, or needs to reset their workspace.
codify-context
Codify knowledge from the current session into the right layer of the context architecture (GC, a repo CLAUDE.md, a path scoped rule, a skill's learned rules, a hook, a tool doc, or auto memory), routing by trigger and admitting to always loaded files only through the placement tests. Use this skill whenever the user says "codify" followed by a topic, wants to capture something they just figured out, asks to document a pattern or convention, or says something like "we should write this down" or "future me needs to know this." Also trigger when the user discovers a gotcha, foot gun, or non obvious behavior worth preserving. Named after the "plan, delegate, assess, codify" Level 4 compounding loop. This is the write in counterpart to `assist:groom-context`, which audits and prunes the same context architecture.
create-presentation
Build a polished reveal.js presentation deck for an internal demo, talk, or share-out. Generates a single-file HTML deck with RYLLC brand styling, served locally via `npm run preso`. Use this skill whenever Forni says "build a presentation", "make a deck", "let's prep a demo", "create a preso", references an upcoming demo or talk that needs slides, or invokes `/assist:create-presentation`. Also trigger when Forni wants to walk through work to an audience and asks how to assemble it. Decks live under `preso/YYYY-MM-DD_<slug>/` in whichever repo the work was done.
draft-applications
Drain the work search queue. Consume queued postings from the Pinole work API (through the pinole CLI) and produce a complete application package per role, one at a time, in this order: fit sanity check, cover letter, application question responses, hiring manager research, follow up email draft, then log the application activity and mark the posting applied once Forni confirms submission. Use whenever Forni says "apply to the queue", "run the applications", "apply to <company>", or queued postings exist after a recruiter sweep. Replaces the retired job-apply skill.
groom-context
Audit and redesign the context architecture (every CLAUDE.md, rules file, learned-rules.md, tool doc, and the auto memory index that loads into Claude Code sessions) so rules are stated once, never in contradiction, and enforced at the point of use rather than scattered, duplicated, or buried. Use this skill whenever Forni says "groom context", "groom-context", "we forgot a basic again", "the context is sprawling", "the rules keep getting lost", "clean up the context", or invokes "/assist:groom-context". Also invoked as a closing step by the monthly path of assist:reflect. This is the cleanup counterpart to assist:codify-context, which writes knowledge into the same architecture.
handle-budget
Categorize and approve YNAB transactions, building a payee rules engine that gets smarter each run. Runs as a dry run by default and never writes without explicit approval. Use whenever Forni mentions YNAB, categorizing spend, cleaning up the budget, approving transactions, the unapproved queue, payee cleanup, or wants a clean read on where money is going. Also trigger for "/assist:handle-budget", "tidy the budget", or "categorize my spending".
keep-alive
Keep the session's prompt cache warm while Forni steps away, with a self paced loop that wakes every 50 minutes and does nothing else unless given a watch task, then end it the moment he is back. Use whenever Forni says "keep alive", "keep this alive", "keep the cache warm", "I'm heading out", "going for a run", "back in an hour", or invokes "/assist:keep-alive", optionally with something to watch while he is gone ("keep alive and watch the landers").
mise
Morning prep sync for Forni's workstation. Pulls latest in ~/Eudaimonia and ~/Eudaimonia/Craft/Development/personal/homebase, then runs homebase's setup.sh to deploy dotfiles and refresh brew, npm globals, IDE extensions, and Claude plugins. Use this skill whenever Forni says "mise", "mise en place", "prep the station", "morning sync", "get the station ready", or otherwise wants his dev environment neat and tidy before the day's work. Also trigger for "/assist:mise". Named after mise en place: everything in its place before service.
permissions
Hoist project-level permissions into user-level settings, collapsing similar entries into wildcards. Use this skill whenever the user says "hoist permissions", asks to clean up their project permissions, wants to promote permissions to user level, or mentions that they're tired of re-approving the same tools across projects. Also trigger when the user says "move permissions up" or asks for help organizing `.claude/settings.local.json`.
plan-meals
Weekly meal planning, shopping list generation, and pantry aware grocery runs. Produces a plant based, seasonal, batch prep friendly meal plan for the week, authored into the Pinole app, plus a consolidated shopping list grouped by store. Use this skill whenever the user mentions meal planning, wants to plan the week's food, asks for a shopping list, wants help figuring out what to cook, mentions batch prep, macros, recipes, a grocery run, a Sprouts or Costco trip, or says things like "back on the healthy eating train" or "kick the takeout habit." Also trigger for "/assist:plan-meals", "meals for the week", or "what should I cook". Prefer invoking this skill even when the user's ask is oblique (e.g., "I want to stop eating out" or "I need to hit my macros this week") since meal planning is usually the underlying need.
plan-training
Training plan scheduling, weekly retrospectives, and training adjacent constraint validation. Use this skill whenever the user mentions training, lifts, runs, swims, yoga placement, recovery days, the recomp block, asking to schedule a training session, or asking to look back / retrospect on a past training week. Also trigger for "/assist:plan-training", "schedule my training", "what does training look like this week", "how did last week go", "training retro", "this week's lifts", or any request that touches the block plan in `Constitution/Fitness/`. Independently usable, and also called by `/assist:plan-week` during Monday planning.
plan-trip
Group trip and getaway planning. Scope the trip, pull live lodging availability, present options with per head cost, verify before booking, research the constraint that actually drives the trip (weather windows, permit and reservation release dates, access rules), hand off the booking, then capture a trip doc and schedule the time sensitive follow ups. Use this skill whenever Forni mentions planning a trip, a getaway, a group house, a cabin or Airbnb or VRBO for a crew, a basecamp for a race or hike or backpacking objective, finding lodging for friends, splitting a house, acclimation lodging, or asks "where should we stay", "find us a place", or "book the house" for an upcoming adventure. Also trigger for "/assist:plan-trip", "plan the Aspen trip", "find a house for the boys", or "we need a place for the loop weekend". Trip records live under `~/Eudaimonia/Craft/Adventure/`; this skill is the workflow counterpart to the Adventure planning conventions documented there.
plan-venture
Direction-setting session for a venture. First-principles positioning (Dunford), adversarial critique walked one finding at a time, brand and naming decisions, a multi-fidelity roadmap, and full artifact true-up (docs, Linear, calendar, Todoist). Use this skill whenever Forni wants to plan a business's direction, asks "what is this business", wants to work through positioning or strategy from scratch, questions whether the ladder is against the right wall, wants a brand or naming workshop, or invokes "/assist:plan-venture". Also trigger for a Monday planning block that turns strategic ("direct the energy before scheduling more work"). Weekly slotting stays in assist:plan-week; this is the deeper, occasional session that decides what the weeks are for.
plan-week
Weekly planning, calendar management, and Monday planning session task slotting. Use this skill whenever the user mentions weekly planning, the Monday planning session (07:00, first thing in the deep work block; it ran on Sundays until 2026-08-30), slotting tasks, finding free time, checking what their week looks like, moving or swapping calendar events, or wants help fitting something into their week. Also trigger when the user asks about V2MOM measure coverage. Training plan scheduling lives in `assist:plan-training`; this skill calls into it during the weekly planning session.
refine-process
Refine a recurring process (a skill's workflow, a checklist, a pipeline of phases) through a structured, iterative pass with the user. Use this skill whenever Forni says "refine this process", "take a pass at this workflow", "the phases feel off", "let's rework how we do X", or asks for a watchful or deliberate redesign of any multi step process. Also trigger when a process refinement emerges mid session (directives like "move phase X before Y" or "merge these steps") and the user wants it done properly rather than ad hoc. The refinement counterpart to `assist:codify-context` (which writes knowledge) and `assist:groom-context` (which prunes it); this skill reshapes workflows.
reflect
Guided reflection at the boundaries Forni looks back on (weekly, monthly, quarterly, yearly). A dialogue-driven retrospective, not a journal reader. Brings the quantitative spine the paper journal misses (movement, overconsumption tally), then reflects by conversation against the V2MOM frame. Use this skill whenever Forni says "reflect", "let's reflect", "reflect on the month", "monthly reflection", "look back on May/the month/the week", "end of month", "retrospective", "retro", "weekly reflection", or invokes "/assist:reflect". Also trigger at quarter or year boundaries when Forni wants to look back. Monthly is the default. Weekly retro is also called by `assist:plan-week` before planning the next week. Quarterly hands off to the V2MOM eval walk.
report-unemployment
File the weekly Colorado unemployment payment request in MyUI+ from the activities ledger in the Pinole work API. Builds the reportable activity slate for the just ended claim week, drives MyUI+ through agent-browser attached to Forni's real Brave, walks the weekly payment request screens, and stops hard at both certifications for Forni's explicit yes. Use whenever Forni says "report unemployment", "request UI payment", "file the weekly claim", "MyUI+", mentions the Monday payment request task, or invokes /assist:report-unemployment. The claimer agent carries this method for background dispatch.
sharpen-saws
Run the weekly sharpen audit that moves collaboration one small step toward Levels 7 and 8 of the agentic engineering hierarchy. Verify each unattended routine fired and was consumed, close or ticket every deferral, take one cut from the always loaded context, groom one flag, and append a one screen log entry to LEVELS.md. Use this skill whenever the user says "sharpen", "sharpen saws", asks to "sharpen our process", or explicitly starts a sharpen session. Paired with the weekly Sharpen Saws block on Wednesdays. The sharpener agent carries this method for background dispatch.
triage-inbox
Triage the Gmail inbox to a settled state. Classify every email, draft a reply for anything needing a response, and turn action-without-response into a Todoist follow-up, then review and execute one email at a time. Handles unsubscribes, recurring-sender filters, and per-sender side actions inline as they come up. Use whenever the user mentions email triage, inbox cleanup, processing the inbox, clearing email, or getting to inbox zero.
wrap
Session wrap. Don't lose the thread, clean everything up, don't leave loose ends in your head. Scans every git repo touched this session for uncommitted or unpushed state, surfaces external commitments (pending replies, calendar holds, contract deadlines) from the recent conversation, prompts for codification of durable learnings, logs each loose end the user triages to Todoist (today if pressing, next Sunday otherwise), summarizes the session, and closes with a compaction ready line. Run it yourself, unprompted, the moment the session reaches its terminal state (the work landed, tickets closed, no question open), with a one line heads up rather than an offer. Also use it whenever the user says "wrap", "wrap up", "wrap the session", "wrap this up", "wrapping up", "clean up before I exit", "signing off", "done for the day", or invokes /assist:wrap. Pairs with /assist:mise as the bookend. Mise opens the kitchen for service. Wrap closes it cleanly after.
linear-lifecycle
Use when working with Linear issues, issue tracking, or project management. Uses the Linear CLI for zero-context issue management as a CLI alternative to MCP.
checkpoint
Save work in progress with commit and push (no PR). Use this when the user wants to save progress, push a checkpoint, or back up current work without creating a pull request.
design
Start work on an issue with branch setup and implementation design. Use this whenever the user wants to begin a new task, start on a ticket, or set up a feature branch for development work.
groom-issues
Groom a Linear team's queue. Two modes, cycle grooming (when the team runs Linear cycles, trim the active cycle to a realistic slate) and backlog grooming (when the team has a backlog without active cycles, triage by priority, staleness, and intent). Use whenever the user mentions Linear grooming, triaging issues, pruning a backlog, sprint grooming, "the cycle is overstuffed", "let's clean up the queue", "groom the backlog", or wants to make decisions across many issues at once. All Linear access goes through the `linear` CLI.
iterate
Address PR review feedback and re-run the CodeRabbit CLI review on the new HEAD. Use this when the user needs to handle PR comments, respond to code review, or iterate on feedback from reviewers.
plan
Refine requirements on a Linear ticket through Socratic dialogue. Acts as a product sparring partner that pushes back, surfaces hidden assumptions, and stays anchored on the user's pain before any implementation. Use this when the user wants to think through a problem, clarify requirements, or evaluate options before starting design work.
review
Create PR for code review. Use this when the user is ready to submit their work, create a pull request, or send code for review.
land
Drive the back half of SDLC autonomously. Run the CodeRabbit CLI review as the gate, watch CI, triage findings, merge (squash), then clean up. The agent (not GitHub) judges when feedback is addressed. Bails to the user on human review, hard CI failure, merge conflict, or time budget exceeded. Default next step after implementation; use when the user says "land it", "ship this", "merge when ready", or invokes /sdlc:land.
ask-questions
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
implement-plan
>
create-plan
Create a scoped, code-backed implementation plan from a todo, spec, issue, review notes, or raw user instructions. Use when the user asks to convert requirements into a proper plan, phased implementation plan, executor handoff plan, or reviewable planning artifact before coding.
review-spec
Review a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
review-implementation
>
code-quality-review
>
interrogator
>
react-to-review
>
handoff-work
>
audit
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
diagnose-issue
Research and define codebase issues before implementation planning. Use when the user provides an issue statement, bug report, Jira ticket, vague problem, proposed solution, runtime symptom, or design concern and wants Codex to inspect the current codebase, validate whether the problem exists, diagnose likely causes, compare solution directions, and produce an evidence-backed problem definition. Do not use when the user asks for a step-by-step implementation plan, direct implementation, or code review of an existing diff.
cursor-cli
>-
Page 1332 of 1715 · 85716 results
