Skip to content

Recently active skills

Trending is calculated from star growth this site has recorded itself. No history is estimated or back-filled.

Not enough history yet: 2 of 7 days recorded. Until then this list is ordered by the most recent content change.

77079 skills

prismaom-network/betayumPrisma schema conventions and migration workflowStars: 0Updated Claude CodeCodexVerifiedInstall
production-readinessom-network/betayumRun all audit checks (RBAC, hooks, design system, tests) and verify buildStars: 0Updated Claude CodeCodexVerifiedInstall
prompt-engineeringom-network/betayumPrompt engineering best practices - invoke with @prompt-engineeringStars: 0Updated Claude CodeCodexVerifiedInstall
stale-worktree-cleanupom-network/betayumUse when cleaning up old git worktrees, removing worktrees whose branches have merged or been abandoned, or dropping orphaned compdev_* Postgres databases. Triggers on "clean up worktrees", "delete stale worktrees", "worktrees piling up", "orphaned databases", "remove unused worktree".Stars: 0Updated Claude CodeCodexVerifiedInstall
trigger-advanced-tasksom-network/betayumComprehensive rules to help you write advanced Trigger.dev tasksStars: 0Updated Claude CodeCodexVerifiedInstall
trigger-basicom-network/betayumOnly the most important rules for writing basic Trigger.dev tasksStars: 0Updated Claude CodeCodexVerifiedInstall
trigger-configom-network/betayumConfigure your Trigger.dev project with a trigger.config.ts fileStars: 0Updated Claude CodeCodexVerifiedInstall
trigger-realtimeom-network/betayumHow to use realtime in your Trigger.dev tasks and your frontendStars: 0Updated Claude CodeCodexVerifiedInstall
trigger-scheduled-tasksom-network/betayumHow to write and use scheduled Trigger.dev tasksStars: 0Updated Claude CodeCodexVerifiedInstall
uiom-network/betayumUse when building or editing frontend UI components, layouts, styling, design system usage, colors, dark mode, or icons.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-analyticsm3dcodie/eng-flowProduction Stage 10 — on-demand rollup report of eng-flow/analytics.jsonl (time/token log) and eng-flow/findings.jsonl (bug counts), both incrementally written by other eng-flow skills. Reports per-story and per-stage totals, tokens by category, cycle time (elapsed vs. active), stage-transition gaps, review/QA rework cycles, and bug rate. Read-only; doesn't instrument itself.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-architecturem3dcodie/eng-flowProduction Stage 3 — takes a saved eng-flow spec and domain model and produces the technical design — tech stack, a tech-labeled system diagram, API contracts, quantified non-functional requirements, deployment topology, and ADRs. This is where technical decisions actually get made; Stages 1 and 2 deliberately deferred all of them here.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-browsem3dcodie/eng-flowGeneral-purpose visual-verification tool wrapping the plugin-bundled Playwright MCP server — navigate a URL, screenshot, check console errors, verify a page/component renders correctly. Usable standalone by any agent/skill in this plugin, any time — not tied to a production-track stage.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-code-reviewm3dcodie/eng-flowProduction Stage 6 — reviews an implemented diff (branch vs. base, or a specific story's commits) across five axes before it ships. Post-implementation counterpart to Stage 3.5's pre-implementation architecture review — this one reviews actual code, not a design doc.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-domain-modelm3dcodie/eng-flowProduction Stage 2 — takes a saved eng-flow spec and turns its named domains into a domain model, data flows, and a conceptual system diagram. No tech stack, no deployment, no API shape — that's Stage 3. Run by an "architect" persona, after eng-flow-spec, before eng-flow-architecture.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-eng-reviewm3dcodie/eng-flowProduction Stage 3.5 — reviews a saved architecture.md against engineering-leadership judgment before it becomes epics/stories/tasks. Catches architecture problems while they're still cheap to fix (before backlog breakdown, before implementation), not a code review — no code exists yet at this point in the track.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-epics-stories-tasksm3dcodie/eng-flowProduction Stage 4 — turns a spec's domains and journeys, cross-checked against the architecture's system diagram, into epics and stories in a project-level backlog (not per-spec — epics/stories outlive any one spec run). Task-level breakdown is separate and on-demand, only generated per-story once the user decides to implement it.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-implementm3dcodie/eng-flowProduction Stage 5 — implements one pending task from a story's tasks.md, one at a time, using an incremental TDD loop (implement, test, verify, commit). Terminal stage after eng-flow-epics-stories-tasks. Whole-story auto mode is not built yet — this only ever does the next single task, then stops.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-mvpm3dcodie/eng-flowMVP mode — the fast, low-ceremony counterpart to the ten-stage production track (PROCESS.md). Captures a one-pager, breaks it into a flat checklist (no epics/stories), gives a ballpark time/token estimate and gets an explicit go/no-go, then runs an auto-continuous implement loop that keeps committing (and, if the user opts in, pushing) until the checklist is done or a hard-stop condition hits, then hands off to eng-flow-ship. Self-triggerable — reuses an existing eng-flow-spec spec.md if one exists instead of re-capturing it, but doesn't require one.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-qam3dcodie/eng-flowProduction Stage 7 — browser-based, front-end-only behavioral QA. Exercises the running app (not the diff) to find bugs a code review can't catch. Drives the browser via the plugin-bundled eng-flow-browse skill — falls back to a guided manual checklist if browser automation is unavailable in a given session. Documents bugs; does not fix them — fixes route through eng-flow-implement.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-retrom3dcodie/eng-flowProduction Stage 9 — blameless retrospective on a shipped (or in-progress) story, capturing durable learnings to a project-level log so future implementation work doesn't repeat the same mistakes. Distinct from a weekly velocity report — this is per-story, root-cause-focused, and only as useful as whether later stages actually consult what it logs.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-shipm3dcodie/eng-flowProduction Stage 8, terminal — ships a feature branch. Gate-checks Stage 6/7 verdicts (code-review.md, qa-report.md) instead of re-reviewing, merges base before a final regression pass, bumps version/changelog if the project tracks them, commits, pushes, and opens a PR. Never deploys to a cloud target — matches local/container/GitHub practice.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-specm3dcodie/eng-flowFront door for new work — routes an idea, a stakeholder-greenlit product, or a feature/story into the right requirements process, interrogates for a spec, optionally runs bounded competitor research, and saves to eng-flow/specs/. Pure requirements only — never asks technical questions except on the feature/story path where code already exists.Stars: 0Updated Claude CodeCodexVerifiedInstall
eng-flow-ui-designm3dcodie/eng-flowProduction Stage 3.6 — takes a saved spec/domain-model/architecture and produces the UI design a UI-touching story needs before Stage 4 exists — a reusable project-level design system, per-journey wireframes, and (once gated) static HTML/CSS mockups. Skipped entirely if the spec's journeys have no UI surface. Between Stage 3.5 (Eng Review) and Stage 4 (Epics/Stories/Tasks).Stars: 0Updated Claude CodeCodexVerifiedInstall
socratic-workshopsmashburger-dev/socratic-workshopLearn by explaining a concept to the agent, receiving one Socratic question or requested hint at a time, and revising the explanation. Use for interactive tutoring, learning from an existing project, or a requested Workbench HTML learning visualization.Stars: 24Updated Claude CodeCodexVerifiedInstall
ask-mattegma-ai/egmaAsk which skill or flow fits your situation. A router over the skills in this repo.Stars: 146Updated Claude CodeCodexVerifiedInstall
broegma-ai/egmaRe-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'. Use /bro to get a plain-language version of the last answer.Stars: 146Updated Claude CodeCodexVerifiedInstall
code-reviewegma-ai/egmaReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".Stars: 146Updated Claude CodeCodexVerifiedInstall
codebase-designegma-ai/egmaShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.Stars: 146Updated Claude CodeCodexVerifiedInstall
coordinate-implementationegma-ai/egmaDrive one ticketed effort through parallel implementation, independent review, serial integration, and one open pull request.Stars: 146Updated Claude CodeCodexVerifiedInstall