n-n-code
UserJust Another Agent skill repository.
Categories
Indexed Skills (47)
agent-skill-generator
Design, create, revise, audit, validate, or optimize reusable agent skills and SKILL.md packages across platforms. Use for trigger precision, structure, progressive disclosure, token efficiency, prompt evals, or converting repeated workflows into portable skills. Do not use for AGENTS.md, skill fusion, or host packaging alone.
agents-md-generator
Create, draft, audit, revise, or migrate root and nested repository AGENTS.md files from repo evidence. Use when the user asks to create or review an AGENTS.md, improve repository coding-agent instructions, convert CLAUDE.md-style guidance into AGENTS.md, or decide instruction scope in a monorepo. Primary for AGENTS.md; use documenter for README, contributor, and other agent-facing documentation.
backend-guidance
Baseline overlay for routine thin HTTP, gRPC, or message-consumer implementation and review; use `backend-systems-guidance` for multi-layer, data-access, transaction, reliability, or trust-boundary work. Compose with matching implementation guidance. Not for outbound-client-only or security-audit tasks.
backend-systems-guidance
Canonical overlay for non-trivial server-side networked implementation and review involving multi-layer architecture, data access, reliability, trust boundaries, or deeper testing; use `backend-guidance` for thin routine handlers. Compose with matching implementation guidance for APIs, queues, repositories, transactions, or auth-sensitive flows.
coding-guidance-bash
Bash implementation and review guidance for automation and repository scripts; not for one-off command execution, POSIX `sh`, or release-workflow design where `project-release-maintainer` is primary. Covers safe quoting, explicit failure handling, process ownership, and maintainable shell boundaries.
coding-guidance-cpp
C++ implementation and review guidance for modern ownership, type safety, API design, and tests; use `coding-guidance-qt` when QObject lifetime, signals and slots, QWidget/model-view behavior, Qt threading, or Qt build tooling is the main concern. Portable across C++17/20/23 repositories and build systems.
coding-guidance-go-tui
Go terminal UI implementation and review guidance for interactive Bubble Tea state machines. Includes Huh only when embedded in Bubble Tea; use `coding-guidance-go` for standalone or one-shot Huh prompts and other non-TUI Go work. Covers Bubbles, Lip Gloss, key bindings, focus, and supported Charmbracelet major versions.
coding-guidance-go
Go implementation and review guidance for non-interactive CLIs, libraries, workers, and services; use `coding-guidance-go-tui` for interactive Bubble Tea and `go-testing-with-testify` for testify-focused test work. Covers errors, contexts, concurrency, package boundaries, standard tests, and measured performance.
coding-guidance-python
Python 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.
coding-guidance-qt
Qt C++ implementation and review guidance for QObject, QWidget/model-view, signals and slots, thread affinity, `.ui` forms, and Qt build tooling; use `coding-guidance-cpp` for non-Qt C++ design. Portable across Qt5/Qt6 repositories with a QWidget desktop focus.
context-engineering
Workflow 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.
development-contract-process
Portable 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.
development-contract-repo-overlay-template
Template 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.
development-contract-system
Build 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.
documenter-coauthoring
Companion overlay to documenter for user-directed, multi-round coauthoring of specs, PRDs, proposals, ADRs, decision docs, and similar technical documents. Use when the user wants to shape or approve structure, set checkpoints, iterate section by section, or preserve decisions across rounds. Document size neither selects nor excludes it. Do not use alone or for autonomous one-pass drafting or review.
documenter
Evidence-backed review, writing, revision, or restructuring of durable READMEs, specs/ADRs, agent guides, and public API/release docs when claims or structure need judgment. Route AGENTS.md to agents-md-generator; add documenter-coauthoring for staged work. Let matching domain skills lead when code, packaging, or release machinery also changes. Not for mechanical copy edits, chat summaries/handoffs, prompt behavior, binary-file work, regulated document control, or docs-site tooling alone.
dream-thinking
Creative retrospective workflow that uses simulated dream imagery and metaphor to defamiliarize recent experience, then turns it into grounded hypotheses and next observations or actions. Use only when the user explicitly asks to dream, sleep on something, use a dream or nightmare lens, or reflect through metaphor. Do not use for ordinary retrospectives, postmortems, first-pass analysis, or as the basis for evidence-critical conclusions.
fuse-skills
Fuse two or more bounded agent skills into one new or explicitly named existing package without accidental capability loss. Use when asked to merge, fuse, consolidate, deduplicate, fold, or unify local, remote (including `skills.sh`), or inline sources into one package. Do not use for runtime composition, single-skill revision without source integration, cross-skill cleanup that keeps separate packages, or an orchestrator that continues delegating.
go-testing-with-testify
Write, review, or harden Go tests using stretchr/testify assert, require, mock, or suite. Use for assertion choice, test doubles, subtests, concurrency, and flake triage in an existing Go test setup. Use coding-guidance-go for production code or non-testify tests and tester-mindset for test strategy without concrete test code.
playwright-testing
Use 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, or CI harnesses; use `setup-playwright`.
prompt-engineering
Prompt 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.
recursive-thinking
Adversarial review workflow for pressure-testing an existing candidate plan, diagnosis, design, argument, proposal, or recommendation. Use when the user asks to challenge its assumptions, run a premortem, play devil's advocate, red-team a non-security decision, or identify what would change the conclusion. Do not use for open-ended exploration (use thinking) or exploit-focused security review (use security as primary).
security-identity-access
Companion overlay used only with `security` when explicitly security-focused review, threat model, or implementation centers on authentication, sessions, recovery, MFA or passkey lifecycle, federation or account linking, identity-provider or recovery callbacks, invitations, or tenant authorization. Never use alone or for routine login, signup, user-model, RBAC, or backend work without a security objective.
security
Evidence-grounded threat modeling, vulnerability review, and secure implementation. Use for explicit security audits or primary risks involving authorization, untrusted input, external requests, parsers/uploads, secrets, sensitive data, isolation, or release integrity. Not for routine implementation or non-security red-teaming. Add `security-identity-access` for identity and tenant authorization.
setup-playwright
Use when adding, extending, or repairing a repo-owned Playwright test harness across Node Playwright Test, Playwright Pytest, or .NET/Java test frameworks. Also use when explicitly persisting `@playwright/cli` developer tooling, or adding or regenerating Playwright Test Agent definitions for a compatible Node Playwright Test harness. Not for live CLI exploration or ordinary spec work in a working harness; use `playwright-testing`.
story-implementation-orchestrator
Coordinate the full story-to-plan preparation workflow across user-story-clarifier, story-repo-scout, and story-implementation-planner. Use when a rough ticket needs clarification, repo scouting, implementation planning, packet validation, partial-packet resumption, or downstream skill routing before coding; avoid direct implementation.
story-implementation-planner
Create a constraint-aware implementation plan from a Ready Story Card and sufficiently evidenced Repo Context. Use when the requested artifact is the plan itself; use story-to-plan-orchestrator for multi-stage preparation, packet completion, resumption, or validation. Avoid story drafting, repo scouting, and direct implementation.
story-repo-scout
Inspect a repository for story-specific implementation evidence, applicable decisions, validation prior art, and bounded planning-critical external primary sources, then produce compact Repo Context. Use for pre-implementation file discovery and greenfield path grounding; use tester-mindset for test strategy and avoid requirements clarification, implementation planning, broad context management, security review, or code changes.
tester-mindset
Testing 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.
thinking
Decision-framing workflow for turning an ambiguous problem or open choice into a recommendation, experiment, or concrete next move. Use when the user wants to explore a vague idea, compare plausible approaches, understand system trade-offs, or decide what to do. Do not use for sustained brainstorming, when the decision is already settled and the remaining work is only implementation, or adversarial review of an existing candidate (use recursive-thinking).
ui-design-guidance
Canonical overlay for graphical UI or frontend redesign, polish-heavy implementation, and deep UX review; use `ui-guidance` for routine changes. Compose with matching implementation guidance when visual direction, accessibility, interaction, responsive behavior, forms, navigation, or data presentation need stronger discipline.
ui-guidance
Baseline overlay for routine graphical UI and frontend changes that preserve the existing design language; use `ui-design-guidance` for redesign, polish-heavy implementation, or deep UX review. Compose with matching implementation guidance. Not for terminal UIs or pure plotting.
user-story-clarifier
Workflow for drafting, rewriting, splitting, and auditing story-level requirements, user stories, feature definitions, definitions of done, and acceptance criteria into unambiguous story cards for humans and coding agents. Use for rough tickets, broad epics, or unclear product behavior; avoid for full PRDs, glossary definitions, and code implementation.
project-config-and-tests
Project overlay for config precedence, defaults, parsing, normalization, path helpers, and deterministic tests at those seams. Not for general test strategy or unrelated test implementation.
project-platform-diagnose
Diagnostic project overlay for environment-dependent build, install, startup, CI, container, headless, terminal, or runtime failures. Not for ordinary logic bugs or known release packaging changes.
project-release-maintainer
Project overlay for release and packaging maintenance across install layout, shipped assets, automation, license and notice alignment, and release docs. Not for content-only documentation or publishing without explicit authorization.
project-vendor-boundary
Project overlay for checked-in or submodule-managed third-party source, provenance, local patches, and the app-owned integration seam. Not for package-manager dependency changes without vendored source.
story-clarifier
Draft, 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.
story-to-plan-orchestrator
Coordinate 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.
deepseek-harness
Use 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.
agentic-sdlc-improvement
Evaluate 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.
agentic-sdlc
Coordinate 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.
chrome-devtools-axi
Use 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.
design-md-author
Author, 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.
jekyll
Understand, 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.
lighthouse
Run 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.
project-core-dev
Project overlay for discovering and reporting repository-specific completion checks for routine repo-owned changes. Use when the validation path is unclear; prefer specialized project overlays for config, platform, release, or vendor concerns.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.