All authors
Claude Skills by n-n-code
github.com/n-n-code45 skills0 installs66 views
- Agent Skill GeneratorCreate or revise reusable agent skills from a problem statement, workflow, or existing skill folder. Use when the user asks to build a skill, design an agent skill for a repo, improve a skill's triggering or structure, validate a skill with representative prompts, audit a skill for token efficiency, or turn a repeated workflow into a portable skill package.Votes: 0GitHub stars: 4
- Agents Md GeneratorCreate or revise repository AGENTS.md files from repo inspection, existing docs, and a small number of high-impact clarifications. Use when the user asks to create an AGENTS.md, improve agent instructions for a repo, convert CLAUDE.md-style guidance into AGENTS.md, or write coding-agent instructions for a repository.Votes: 0GitHub stars: 4
- Backend GuidanceOverlay for server-side networked code — HTTP handlers, gRPC services, message consumers. Use alongside the repo's implementation skill when implementing or reviewing backend logic.Votes: 0GitHub stars: 4
- Backend Systems GuidanceCanonical overlay for non-trivial server-side networked code that needs multi-layer architecture, data-access, reliability, trust-boundary, or deeper testing discipline. Use alongside the repo's implementation skill for backend services, APIs, middleware, queues, repositories, transactions, auth-sensitive flows, or backend refactors; use `backend-guidance` for thin routine handler work.Votes: 0GitHub stars: 4
- Coding Guidance BashBash implementation and review skill. Use when writing, modifying, refactoring, or reviewing Bash scripts, especially automation and repo tooling that need defensive error handling, safe quoting, predictable control flow, and maintainable shell boundaries. Portable across Bash-based repos and script stacks.Votes: 0GitHub stars: 4
- Coding Guidance CppC++ implementation and review skill. Use when writing, modifying, refactoring, or reviewing C++ code, especially modern C++17/20/23 code that needs strong ownership, type safety, and testable design. Portable across C++ repos and build systems.Votes: 0GitHub stars: 4
- Coding Guidance Go TuiGo terminal UI implementation and review skill. Use when writing, modifying, refactoring, testing, or reviewing interactive Go TUIs built with Charmbracelet Bubble Tea, Bubbles, Lip Gloss, embedded Huh forms, Charm stack v2, tea.Model, tea.Cmd, key bindings, focus state, terminal layouts, or terminal screen state machines. Portable across Go TUI repos.Votes: 0GitHub stars: 4
- Coding Guidance GoGo implementation and review skill. Use when writing, modifying, refactoring, testing, optimizing, or reviewing Go code, especially production Go that needs clear errors, context propagation, concurrency safety, interface discipline, package boundaries, REST or gRPC service boundaries, standard-library testing, pprof-backed performance work, logging, and tooling discipline. Portable across Go repos and service stacks.Votes: 0GitHub stars: 4
- Coding Guidance PythonPython implementation and review skill. Use when writing, modifying, refactoring, or reviewing Python code, especially production Python that needs clear contracts, type safety, testability, and maintainable module boundaries. Portable across Python repos and tooling stacks.Votes: 0GitHub stars: 4
- Coding Guidance QtQt implementation and review skill. Use when writing, modifying, refactoring, or reviewing Qt C++ QWidget desktop code, especially Widgets, `.ui` forms, Designer-generated UI, models, `QAbstractItemModel`, signals and slots, `eventFilter`, `QThread`, CMake-based Qt5/Qt6 builds, layout-heavy UI, and QObject lifetime or thread-affinity problems. Portable across Qt-based C++ application repos.Votes: 0GitHub stars: 4
- Context EngineeringWorkflow for context packets, context audits, compaction, handoffs, session memory, and deciding what AI-agent context to load, retrieve, trim, summarize, refresh, or omit. Use for context rot, context flooding, stale or missing context, task switching, and long-running agent sessions. Do not use when prompt wording, repo file discovery for a story card, or AGENTS.md authoring is the main artifact.Votes: 0GitHub stars: 4
- Development Contract ProcessPortable workflow for repos that require tracked change contracts, verifier evidence, and smallest-proof validation. Use when a repo has a contract policy file or enforced feature-plan checker.Votes: 0GitHub stars: 4
- Development Contract Repo Overlay TemplateTemplate for authoring or revising the thin repo-local overlay generated by the development contract system. Use when writing overlay guidance that names a target repo's policy path, plan directory, checker command, lifecycle helper, or validation profiles; use `development-contract-process` for ordinary work in a repo that already has the system.Votes: 0GitHub stars: 4
- Development Contract SystemBuild a portable change-contract system for any repository. Use when creating or porting a repository workflow based on tracked feature records, lifecycle directories, a policy file, a checker, a lifecycle transition helper, and aligned docs/tests.Votes: 0GitHub stars: 4
- Documenter CoauthoringCompanion overlay for multi-round collaborative drafting of large specs, proposals, decision docs, and similar documents. Use when the workflow needs structured context gathering, explicit outline approval, section-by-section iteration, and reader-testing rather than a direct documentation pass.Votes: 0GitHub stars: 4
- DocumenterBaseline overlay for substantial documentation authoring or restructuring: README, specs, ADRs, tutorials, how-to guides, reference docs, explanations, API docs, code comments, changelogs, and agent-facing docs. Use when the agent should classify doc type, ground claims in repo truth, and validate examples before finishing.Votes: 0GitHub stars: 4
- Dream ThinkingReflective sleep-and-dream heuristic for learning from recent experience. Use when the user asks to sleep on something, dream about it, reflect overnight, learn from yesterday, or extract lessons after a meaningful task, conversation, or debugging session. Avoid for first-pass analysis, simple factual lookups, direct execution, or tasks that do not benefit from reflection.Votes: 0GitHub stars: 4
- Fuse SkillsCombine 2 or more agent skills into one new merged skill without duplicated guidance or lost capability. Use when the user asks to merge, fuse, consolidate, deduplicate, or unify multiple local skills, `skills.sh` skills, or a mix of both into a single portable, precision-dense skill package. Do not use for ordinary multi-skill composition unless the goal is to create a new fused skill.Votes: 0GitHub stars: 4
- Go Testing With TestifyUse when writing, reviewing, or hardening Go tests that rely on stretchr/testify — `assert`, `require`, `mock`, and `suite` — including table-driven tests, subtests, parallel tests, mocks versus hand-written fakes, error-wrap assertions, and flaky test triage with `-race` and `-count`.Votes: 0GitHub stars: 4
- Playwright TestingUse for explicitly requested live browser investigation with `playwright-cli`, or for writing, debugging, reviewing, or hardening Playwright tests in an existing working harness across Node, Python, .NET, or Java. Covers flake triage, locator refinement, visual and responsive checks, test structure, fixtures, auth-state use, and mock boundaries. Generic ad hoc Chrome work defaults to `chrome-devtools-axi`. Not for installing or repairing runner config, browser binaries, reusable-auth plumbing...Votes: 0GitHub stars: 4
- Project Config And TestsOverlay for config contracts, defaults, path helpers, and deterministic test coverage. Use alongside the repo's principle skill when the main task is config behavior or test coverage.Votes: 0GitHub stars: 4
- Project Core DevOverlay for day-to-day feature work and bug fixes in repo-owned code. Provides a validation checklist for build, test, format, and analysis. Use alongside the repo's principle skill.Votes: 0GitHub stars: 4
- Project Platform DiagnoseOverlay for environment-sensitive diagnosis — service startup, install issues, platform integration, headless/container behavior, and runtime smoke checks. Portable across repos where build, install, or runtime behavior depends on the local platform.Votes: 0GitHub stars: 4
- Project Release MaintainerOverlay for release-facing docs, install layout, workflows, licenses, and hygiene scripts. Portable across repos with a release/packaging pipeline. Use for publication-facing changes.Votes: 0GitHub stars: 4
- Project Vendor BoundaryOverlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.Votes: 0GitHub stars: 4
- Prompt EngineeringPrompt engineering workflow for designing, rewriting, debugging, evaluating, and optimizing LLM prompts, system prompts, developer prompts, few-shot examples, structured-output instructions, tool-use prompts, and prompt eval cases. Use when prompt behavior, reliability, safety, cost, latency, or model fit is the main task. Do not use for generic prose editing, model selection alone, or ordinary documentation work with no prompt artifact.Votes: 0GitHub stars: 4
- Recursive ThinkingRecursive self-questioning heuristic for stress-testing a plan, diagnosis, design, review, or recommendation before acting. Use when the user asks to use recursive thinking, go deeper, interrogate assumptions, pressure-test an approach, ask why/how questions, or find what would change the conclusion. Avoid for simple factual lookups or low-ambiguity tasks.Votes: 0GitHub stars: 4
- Security Identity AccessCompanion overlay for the local `security` workflow skill when the task centers on authentication, sessions, identity recovery, or tenant-scoped access boundaries. Use with `security` for session handling, verification and reset flows, MFA, invitation logic, callback-origin trust, and organization or tenant boundary enforcement.Votes: 0GitHub stars: 4
- SecuritySecurity workflow skill for repo-grounded threat modeling, exploit-focused security review, and secure-by-default implementation guidance. Use when the user explicitly asks for security work, or when security properties are the primary concern in a high-risk change. Do not trigger for ordinary code review, routine endpoint work, or general backend implementation just because a repo contains APIs, auth, or secrets.Votes: 0GitHub stars: 4
- Setup PlaywrightUse when adding, extending, or repairing a repo-owned Playwright E2E harness across Node `@playwright/test`, Playwright Pytest, or .NET/Java test frameworks — including browser installation, harness config, auth reuse plumbing, package placement, or CI smoke/sharding setup. Not for ordinary spec debugging once the harness already works; route that to `playwright-testing`.Votes: 0GitHub stars: 4
- Story Implementation PlannerModel-aware implementation planning workflow for turning a clarified story card plus repo context into an actionable plan for a human or coding agent. Use after user-story-clarifier and story-repo-scout when a story needs ordered implementation steps; avoid for story drafting, repo scouting alone, or direct code implementation.Votes: 0GitHub stars: 4
- Story Repo ScoutRepo scouting workflow for using a story card, ticket, or acceptance criteria to scour the current repository, find relevant files and file paths, and append compact implementation context. Use before coding when a story needs repo context; avoid for story drafting, broad architecture review, security review, or implementation.Votes: 0GitHub stars: 4
- Tester MindsetTesting mindset skill for context-driven test strategy, exploratory testing, validation design, acceptance criteria, oracles, weak-test detection, edge cases, heuristics, checklists, and evidence review for code, products, plans, or claims. Use when the user asks what to test, how to test, whether evidence is enough, or to bring a tester mindset. Do not use for merely running an existing test command.Votes: 0GitHub stars: 4
- ThinkingStructured thinking skill. Merges ideation, systems analysis, critical reasoning, and convergent planning. Use when a user needs to explore and narrow a vague idea, challenge assumptions, compare approaches, or converge on a practical next move in the same pass. Do not use when sustained divergence alone is the goal or when a candidate plan already exists and needs adversarial stress-testing.Votes: 0GitHub stars: 4
- Ui Design GuidanceCanonical overlay for graphical UI and web frontend work that is redesign-heavy, frontend-polish-heavy, or UX-review-heavy. Use alongside the repo's implementation skill when visual direction, accessibility, interaction quality, responsive behavior, forms, navigation, or data presentation need stronger design discipline; use `ui-guidance` for routine UI changes.Votes: 0GitHub stars: 4
- Ui GuidanceOverlay for graphical UI and web frontend code. Use alongside the repo's implementation skill when implementing or reviewing UI changes.Votes: 0GitHub stars: 4
- Deepseek HarnessUse for DeepSeek Harness (`dsh`) installation, operation, configuration, automation, extension, troubleshooting, or source-checkout maintenance across profiles, patches, plugins, Web/headless/SDK/ACP surfaces, and Cordis extension points. Not for generic DeepSeek API integration or reusable SKILL.md authoring; use only as a companion when `prompt-engineering`, `security`, `project-platform-diagnose`, or `project-release-maintainer` is primary.Votes: 0GitHub stars: 4
- Story ClarifierDraft, synthesize, rewrite, tighten, or split rough tickets, conversations, user stories, feature definitions, and acceptance criteria into testable story cards or split story sets, or audit existing story inputs with a separate readiness report. Use for ambiguous story-level product behavior or when supplied discussion and artifacts must be consolidated without interviewing; not for PRDs, test strategy, repository scouting, implementation planning, or coding.Votes: 0GitHub stars: 4
- Story To Plan OrchestratorCoordinate multi-stage story-to-plan preparation across story-clarifier, story-repo-scout, and story-implementation-planner. Use for complete implementation-ready handoffs, two or more missing stages, split-slice selection, partial-packet resumption, consistency validation, or stale-stage recovery before coding; use a component skill for one requested artifact and implementation guidance for code changes.Votes: 0GitHub stars: 4
- Agentic Sdlc ImprovementEvaluate and improve repeated agentic software-development workflows using development traces, diffs, review feedback, incidents, and eval results. Use for recurring delivery failures, handoff or verification problems, and evidence-backed changes to how coding agents work. Not for delivering one change, a prompt-only rewrite, context-only repair, general agent-product evaluation, or building an automation platform.Votes: 0GitHub stars: 4
- Agentic SdlcCoordinate end-to-end or resumed multi-stage software delivery from intent through implementation, verification, review, release, and maintenance. Use when an agent must carry a change across lifecycle stages, recover interrupted delivery, or assess that delivery workflow. Not for a single planning, coding, testing, or handoff artifact, building agent infrastructure, or improving repeated development workflows; use agentic-sdlc-improvement for the latter.Votes: 0GitHub stars: 4
- Chrome Devtools AxiUse the chrome-devtools-axi CLI to operate Chrome or investigate live page behavior. Default for ad hoc browsing, forms, rendered extraction, screenshots, DOM/CSS, console/network failures, responsive behavior, and performance or memory questions. Excludes static-only fetching, direct-MCP-only requests, explicitly selected other browser tools, and Playwright tests or harness setup.Votes: 0GitHub stars: 4
- Design Md AuthorAuthor, revise, or review visual DESIGN.md/design.md files, or explain an interface's visual rules without edits. Use source files, images, tokens, or a brief to document web, mobile, or desktop design decisions and reusable UI patterns. Excludes software architecture, UI implementation, and repository agent instructions.Votes: 0GitHub stars: 4
- JekyllUnderstand, review, design, implement, and troubleshoot Jekyll pages and sites using Liquid, front matter, layouts, includes, collections, themes, and assets. Use for conceptual Jekyll questions, tracing page rendering, creating or redesigning Jekyll pages, focused theme overrides, static HTML conversion to Jekyll, or relevant build failures. Not for Shopify Liquid, other site generators, prose-only editing, DESIGN.md authoring, or deployment operations alone.Votes: 0GitHub stars: 4
- LighthouseRun and interpret Google Lighthouse audits for performance, accessibility, best practices, and SEO; compare reports, diagnose and verify improvements, audit authenticated user flows, and configure Lighthouse CI budgets and regression gates. Not for general browser debugging, Playwright test or harness work, backend load testing, custom audit/plugin development, or the Lighthouse ticketing service.Votes: 0GitHub stars: 4