Coding & Dev Tools

urmzd Skill

Cuts releases and validates changelogs across the workspace. Use when preparing or auditing a release.

stunspot Bundle

🌿 Cannabis health, climate, and yield.

gadgetmies Skill

Use when making any code change in track-feature-extractor or dj-automation — before committing, when choosing which tests to run, when authoring tests, and when preparing a worktree branch for merge. Covers WIP vs clean commits, atomic history, relevant-subset vs full-suite test runs, and state-isolated parallel-safe tests.

openadminos Bundle

Use when the user wants a handover summary, shift-change notes, or a paste-ready recap of what this session investigated and decided.

openadminos Bundle

Use when the user reports something broken, failing, or misbehaving in the tenant and needs structured incident triage.

presidenteog Skill

Use when written text reads like AI output and needs to sound human — removing the tells (overused transitions, hedging, inflated vocabulary like "delve/robust/comprehensive", uniform sentence rhythm, em-dash overuse, empty summaries) while keeping the meaning. For blog posts, captions, emails, docs, scripts.

presidenteog Skill

The reference that makes a red-green loop produce tests worth keeping, what a good test is, confirming the seams under test before writing any, and the three anti-patterns that make tests break on refactors or pass by construction. Use when writing or reviewing tests, doing red-green-refactor, or deciding what to test. Complements the loop itself (superpowers:test-driven-development drives red-green); this is the quality gate on what it produces.

presidenteog Skill

Design vocabulary for deep modules, a lot of behaviour behind a small interface placed at a clean seam and testable through that interface. Use when designing or reshaping a module's public interface, deciding where a boundary goes, judging whether an abstraction earns its keep, or when another skill needs the module / interface / depth / seam terms. A reference to consult, not a session to run.

presidenteog Skill

Bootstrap a project's visual identity using DESIGN.md files — plain-text brand design systems that AI agents read to generate consistent UI. Pick a reference from the awesome-design-md collection or generate a custom one from scratch.

presidenteog Skill

Use whenever the deliverable is *found* material rather than *generated* material — real examples, reference images, prior art, competitor work, source collections. Visual references first (GFX, UI, thumbnails, brand, packaging, web layout), then code/implementation examples and written sources. Gives the multi-angle query fan-out, per-source-type phrasing, the reject list, the verification rule, and where findings land. Use it on "find examples of X", "get me references for X", "who does X well", "show me how others do it", "busca referencias de X" — and use it even when the request looks like one quick web search, because firing a single query and reporting whatever ranks first is exactly the failure this prevents. Do not answer these from memory.

presidenteog Skill

Use when writing or updating a Game Design Document — defining the core gameplay loop, mechanics, onboarding, and progression from a concept, or documenting an existing game's systems for a team. Trigger when a project has no GDD yet, or when a new mechanic needs a formal spec before implementation.

openadminos Bundle

Use when the user asks how healthy or secure the tenant is, says posture, risk, score, "how are we doing", or wants a scored Microsoft 365 tenant snapshot.

openadminos Bundle

Use when the user proposes tenant writes or asks to create, update, delete, assign, disable, remediate, grant, revoke, or execute Microsoft Graph changes.

openadminos Bundle

Use when the user poses a live tenant state question when no more specific Greybeard skill matches, including guest accounts, disabled accounts, or simple user and group counts.

openadminos Bundle

Use when the user asks about Entra users, groups, memberships, dynamic rules, orphaned groups, naming hygiene, cleanup candidates, or identity inventory.

openadminos Bundle

Use when the user needs Microsoft Graph mechanics, beta default behavior, explicit beta requests, pagination, batching, throttling, OData query design, or token-efficient call patterns.

openadminos Bundle

Use when the user asks to sanity-check, rehearse, pressure-test, or get grilled on a planned tenant change before executing it.

farzammohammadi Bundle

Work Diary

farzammohammadi Bundle

Conducts post-implementation review covering test coverage, lint, type checks, test fixes, and local testing preparation. Runs all automated verification, identifies gaps, fixes issues, and presents a testing checklist so the user can verify the work manually. Use this skill after implementation and commits are done — as the final quality gate before creating an MR. Also use when the user says "review this", "check my work", "run the checks", "verify everything", "is this ready", or "final review". Pairs with /commit (before) and /glab-mr-manager (after).

farzammohammadi Bundle

Reflect on a skill's performance and iterate on improvements. Use after running any skill to identify gaps and refine it.

farzammohammadi Bundle

Review git diffs against comprehensive refactoring principles. Use when user wants code review, refactoring suggestions, or mentions reviewing changes.

farzammohammadi Bundle

Collaborative, puzzle-piece-based approach to refining resumes, LinkedIn bios, and professional content. Use this skill whenever the user wants to improve, refine, polish, rewrite, tighten, or workshop any resume content (summaries, bullet points, experience sections, headlines), LinkedIn bios or about sections, cover letters, or any professional self-presentation writing. Also trigger when users share resume text and ask for feedback, want to make wordy bullets more concise, are preparing job application materials, or ask to 'make this sound better' for professional contexts. Trigger even for partial requests like 'help with this bullet' or 'does this summary work?'

presidenteog Bundle

Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.

presidenteog Skill

Use when a problem's answer depends on a chain of prior conclusions and jumping straight to one risks skipping a step — before answering, when it's unclear where to start, or when an earlier reasoning error needs to surface at the step that caused it.

presidenteog Bundle

Stand up a three.js scene: import maps and the three/addons path, the Scene/PerspectiveCamera/WebGLRenderer trio, the setAnimationLoop render loop, responsive resize, and OrbitControls. Use when starting or debugging a three.js app — when the user mentions three.js, THREE.Scene, WebGLRenderer, PerspectiveCamera, the render loop, resizing, or OrbitControls. For models use threejs-gltf-loading; for materials/lights use threejs-materials-lighting.

presidenteog Skill

Use when a brand message, landing page or pitch is unclear or isn't converting — the copy talks about the brand instead of the customer, or there's no one-sentence answer yet to what the business actually does for someone.

aaryan1524 Bundle

PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.

presidenteog Skill

Use for genuinely large or multi-session work — a build spanning many phases, a migration, anything likely to survive a /clear or a context compaction — where the plan needs to live on disk rather than in the conversation. Not for ordinary tasks; a quick fix or single-session job doesn't need this.

presidenteog Skill

Use when driving PowerShell on this machine — before trusting a failed exit status, before combining a heredoc with a deletion in one call, or when writing a file another tool will parse.

presidenteog Skill

Use when about to redesign or restyle a UI surface the user has already seen, or when one pass bundles two or more separable visual changes.

presidenteog Bundle

Use when writing or reviewing Kotlin coroutine scope ownership, init launches, non-suspending launch APIs, runBlocking, cancellation, StateFlow, SharedFlow, Channel, stateIn, SharingStarted, state updates, or one-shot events.

lushengguo Skill

启动 KCEX Spot 连接测试环境，观察做市行为和订单管理，检查限流/铺单/模式切换是否正常

wtchrs Skill

Use when creating an ADR (Architecture Decision Record) or managing the status, relationships (Extends, Amends, Supersedes, Related), links, or decision history of existing ADRs. Do not use for architecture exploration or implementation-only work.

cjbuilds Skill

Plan and execute implementation work with proportionate evidence, the smallest complete change, risk-based verification, and a firm stopping point. Use when building, fixing, changing, or reviewing a system where overplanning, speculative work, rebuilding, or incomplete validation could waste effort or weaken the result.

stefancgillberg Bundle

{{description}}

stefancgillberg Skill

Systematic root cause analysis using lean methods (5 Whys, Ishikawa, Gemba). Use when encountering unexpected behavior, errors, or defects to find and fix the true root cause rather than symptoms.