All authors
Claude Skills by susomejias
github.com/susomejias32 skills0 installs0 views
- Find SkillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.Votes: 0GitHub stars: 13
- Improve Codebase ArchitectureFind deepening opportunities in a codebase, informed by the project's own domain language and prior design decisions. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.Votes: 0GitHub stars: 13
- Issue Root ResolutionResolve a verified cluster of Rembric issues from causal root to evidence-gated closure. Use after systemic triage identifies a shared root, or when the user asks to attack issues at the root, create a mechanism map, plan a deletion-first fix, or close a fixed/stale issue cluster. Use `diagnose` for a single defect whose reproduction is not yet established.Votes: 0GitHub stars: 13
- Mcp BuilderGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Votes: 0GitHub stars: 13
- Next Best PracticesNext.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundlingVotes: 0GitHub stars: 13
- Next Cache Components AdoptionTurn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work through a flood of blocking-prerender / instant validation errors, run the `cache-components-instant-false` codemod, or decide between opting routes out with `export const instant = false` and fixing them in place.Votes: 0GitHub stars: 13
- Next Dev LoopVerify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.Votes: 0GitHub stars: 13
- Npm Security Best PracticesApply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.Votes: 0GitHub stars: 13
- Openspec Apply ChangeImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.Votes: 0GitHub stars: 13
- Openspec Archive ChangeArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.Votes: 0GitHub stars: 13
- Openspec ExploreEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.Votes: 0GitHub stars: 13
- Openspec ProposePropose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.Votes: 0GitHub stars: 13
- Plugin SettingsThis skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.Votes: 0GitHub stars: 13
- Plugin StructureThis skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.Votes: 0GitHub stars: 13
- Rembric Dashboard UiRembric dashboard UI work (dark monochrome zinc surfaces, lime accent, Geist type, Spectrum data-tables) — building / editing / extending pages, styles, components, modals, tables, filters, pagination, mobile responsive, destructive confirmations. Use when the user asks for changes under `apps/web/src/app/dashboard/` or `apps/web/src/components/dashboard/`, mentions Rembric design tokens (lime, zinc, command bar, StatusPill, hl-lime, data-table), or requests a new dashboard page / form / table.Votes: 0GitHub stars: 13
- Rembric Plugin DevelopmentApply when creating, modifying, or reviewing any Rembric agent plugin. Triggers on changes under `apps/plugin/`, on new clients added alongside Claude Code / Codex CLI / Hermes Agent / opencode / Pi, on edits to `apps/plugin/mcp-bridge/`, `apps/plugin/bin/rembric-plugin-core.mjs`, per-client manifest changes, or plugin install/uninstall scripts. End-to-end validation against a local dev server (`pnpm run dev`, host Next.js on :3000) is mandatory whenever local testing is feasible.Votes: 0GitHub stars: 13
- Rembric Smoke TestsEnd-to-end smoke against the local rembric dev server (`pnpm run dev`, host Next.js dev on :3000). Apply when the user says "smoke", "probar contra docker", "dev:up", or after applying an OpenSpec change that touches HTTP (`apps/web/src/app/api/`), MCP tools (`packages/mcp/src/`), or DB migrations (`packages/db/src/migrations/`). Encodes bring-up, readiness verification, probe pattern and teardown — not the probes themselves.Votes: 0GitHub stars: 13
- Rembric Tui Installer E2eRunnable end-to-end validation playbook for the Rembric TUI installer — catch breakage before merging/deploying, AND a sandboxed manual walkthrough to evaluate/iterate its UI/UX without polluting your real env. Apply before shipping any change touching `apps/plugin/install.sh`, the repo-root `install.sh` shim, any per-client `install.sh`/`uninstall.sh`, or distribution docs, or when you want to preview/try/demo the installer and polish how it looks and feels. Layered: CI-safe headless (vitest...Votes: 0GitHub stars: 13
- Rembric Tui InstallerThe Rembric TUI installer contract — the single, canonical install/setup/upgrade/uninstall path (`apps/plugin/install.sh`, fronted by the repo-root `install.sh` shim). Apply when touching `install.sh`, the root shim, any per-client `install.sh`/`uninstall.sh`, `marketplace.json`, or distribution docs (README, `docs/agents.md`, plugin/client READMEs). Covers the orchestrator model, what must not break, and where the source of truth lives. For running the validation suite, use `rembric-tui-inst...Votes: 0GitHub stars: 13
- Source Command Opsx ApplyImplement tasks from an OpenSpec change (Experimental)Votes: 0GitHub stars: 13
- Source Command Opsx ArchiveArchive a completed change in the experimental workflowVotes: 0GitHub stars: 13
- Source Command Opsx ExploreEnter explore mode - think through ideas, investigate problems, clarify requirementsVotes: 0GitHub stars: 13
- Source Command Opsx ProposePropose a new change - create it and generate all artifacts in one stepVotes: 0GitHub stars: 13
- Sqlite Database ExpertExpert in SQLite embedded database development for Tauri/desktop applications with focus on SQL injection prevention, migrations, FTS search, and secure data handlingVotes: 0GitHub stars: 13
- Systems ThinkerCall this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.Votes: 0GitHub stars: 13
- TestingPragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library.Votes: 0GitHub stars: 13
- Zero Tech DebtRework a change as if the intended UX and architecture had existed from day one — deleting compatibility cruft, dead branches, and accidental complexity instead of patching around them. Use when refactoring, cleaning up after a feature lands, removing flags, collapsing legacy paths, or when the user says the code "should look like X from scratch".Votes: 0GitHub stars: 13
- Openspec Archive ChangeArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.Votes: 0GitHub stars: 13
- Openspec Apply ChangeImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.Votes: 0GitHub stars: 13
- Openspec ExploreEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.Votes: 0GitHub stars: 13
- Openspec ProposePropose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.Votes: 0GitHub stars: 13
- Thermo Nuclear Code Quality ReviewRun an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.Votes: 0GitHub stars: 13