Narumiruna Skills

Use when implementing a non-trivial, observable behavior change with TDD under explicit ecosystem production-path and test-isolation boundaries. Do not apply red-first mechanically to static configuration, wiring, metadata, or production code outside the defined boundary.

Create, revise, or review prompts and agent instructions using the user-specified model or otherwise the detected runtime model to select a matching reference, with general principles only when the model is unknown or not covered.

Decide whether IMRaD fits, review an IMRaD draft, transform mixed material into IMRaD, or draft a new evidence-traceable IMRaD output without fabricating results.

Review diffs, pull requests, commits, patches, or source files for correctness, baseline security, performance, maintainability, tests, and integration risk. Use for ordinary read-only review, edge-case audits, PR preflight, and reviewer simulation; use audit-code-security when security is the primary objective, and harden-code-paths to fix confirmed failure modes.

Draft, execute, or track lean, verifiable implementation plans for non-trivial migrations, refactors, PR splits, task checklists, and other work with sequencing, tradeoffs, unknowns, or risks, and delete them when complete; use write-roadmap for strategic direction and skip small obvious tasks.

Inspect Jira or prepare and perform precisely authorized Jira mutations with ankitpokhrel/jira-cli (`jira`), including issues, comments, worklogs, epics, sprints, releases, projects, boards, and script-friendly output.

Interview the user one decision at a time to stress-test a plan or design until goals, constraints, assumptions, tradeoffs, risks, and verification are explicit. Use only when the user asks to be grilled or names “grilling designs.”

Create, revise, review, or track concise, outcome-oriented product and system roadmaps with phased milestone checkboxes and evidence-based progress, and delete them when complete; use write-plans for executable task planning and implementation tracking.

Inspect, launch, configure, validate, and troubleshoot an installed Ghostty terminal, including helper CLI actions, keybind actions, themes, fonts, configuration files, and platform-specific behavior.

Create, review, audit, migrate, or update scoped AGENTS.md files with clear rules, verified commands, action limits, instruction order, and checks that prove the work is done. Use also when verified, durable repository guidance emerges during authorized work and should be captured at the narrowest applicable scope.

Use when asked to proactively harden a specific code path by confirming and fixing plausible edge-case, boundary, failure-mode, or lifecycle bugs; to fix a confirmed security finding; or to check nearby same-pattern regression risks. Use audit-code-security first for broad threat analysis or unverified security alerts.

Inspect local Git changes, draft or validate Conventional Commit messages, choose types/scopes, explain breaking changes, or create a focused commit from the actual selected diff.

Write, revise, structure, or validate Marp/Marpit Markdown slides, including directives, layouts, themes, templates, and rendered-deck checks. Use for slide authoring when palette or illustration design is not the primary task.

Create or revise complete Marp/Marpit slide decks, coordinating narrative, slide authoring, color systems, and Mermaid or SVG visuals with rendered validation.

Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use review-code for ordinary review with baseline security coverage and harden-code-paths for fixing confirmed findings.

Create, name, rename, revise, or review agent skills for clear triggers, safe workflows, strong checks, lean content, and easy discovery, and score or numerically compare skills only when the user explicitly asks.

Design, adapt, generate, or validate slide color systems and semantic palettes, including brand-color integration, usage roles, contrast evidence, and presentation-environment caveats.

Use when the user asks for a detailed, beginner-friendly, or step-by-step explanation; wants to understand how or why something works; asks to unpack a concept, issue, PR, code change, system, error, document, or technical decision; or says to explain it like teaching a child.

Manage Python projects and standalone scripts with uv, including setup, dependencies, execution, quality gates, locking, builds, and release preparation. Use for `uv run`, `uv add`, inline script metadata, packaging, or an explicitly requested publish workflow.

Prepare and publish one explicitly authorized public Telegra.ph article through the official Telegraph API, including safe node conversion, optional account setup, credential handling, and page verification.

Create, revise, convert, or validate Mermaid diagrams, including flowcharts, sequence, ER, class, state, Gantt, and optional SVG rendering for documents or slides.

Design, review, or implement accessible user interfaces and end-to-end digital experiences, including screens, components, navigation, information architecture, workflows, system states, and interaction behavior. Use bounded surface mode for focused UI work; substantial cross-surface or product-level experience changes require an approved proposal before implementation.

Create, revise, embed, or troubleshoot accessible SVG diagrams and illustrations for slide decks, documents, and other static artifacts, with portable sizing, layout, style, and validation guidance.

Run one-shot Google Gemini research through the official Google GenAI Interactions API with Google Search, Google Maps, or URL Context grounding and inspect citation evidence. Use when Codex needs current web grounding, place or local recommendations, answers about specific public HTTP(S) URLs, or an explicit Gemini/Google GenAI grounded response.

Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.