Total 58,115 skills
Showing 12 of 58115 skills
This skill should be used when the user asks to "add tilemap", "create a level", "Tiled editor", "tile collision", "object layer", "create map", "tilemap not showing", "level design", "tile layer", "game map", "spawn point", "trigger zone", or "map collision".
Orchestrates modular PyTorch profiler trace analysis with TraceLens: generates perf reports, prepares category data, runs system-level and compute-kernel subagents in parallel, validates outputs, and writes a prioritized stakeholder report (analysis.md). Use when the user asks to follow the analysis orchestrator, run the agentic analysis workflow, analyze a trace, compare two traces, or mentions standalone or comparative TraceLens analysis.
Recover lost Claude Code session context by merging duplicate project directories. Finds session/memory dirs under ~/.claude/projects/ that point at the same logical project from different cwd-encoded paths (e.g. /mnt/work/foo vs ~/Projects/foo cwd produces two separate namespaces). Unifies memory into the canonical dir, archives orphaned jsonl transcripts, and captures the lesson as a feedback memory so the split doesn't repeat. Use when: 'merge sessions', 'recover lost context', 'fix duplicate session dirs', 'session memory split', 'memory dir is empty but I added things', 'two project dirs', 'recover legacy memories from before a folder move', 'stale orphan memory namespace', or any time you find a populated memory dir at the "wrong" path and an empty one at the canonical path.
You are a frontend designer-engineer, not a layout generator.
(NS) Playwright reverse-prototyping face — capture live UI, then create or evolve a single prototype/ tree (git history; never v1/v2 copies). Use when prototyping from a URL, reversing a screen into prototype/, evolving an existing prototype, AS-IS flows/fields, or "prototype this app/page". Do NOT use for normative appearance MDs only (ns-proto-visual-guide), full SDD (ns-spec-driven), bare code fixes (ns-coder), or brownfield prepare (/ns-harness prepare).
Build a throwaway UI prototype to react to before committing. Prefers the /design canvas; falls back to a self-contained HTML artifact when /design is not available.
(NS) Gated PM workflow — clarify, structure, RICE/WSJF, sprint plan, PERT/Monte Carlo forecast; risk, status, meeting, OKR. Also commercial budget (orçamento, Function Points, proposta comercial; COSMIC/CFP only if asked), triple productivity delivery schedule (cronograma P100/P85/P50, prazo, when we deliver), and requirements enricher / grill-me for GitLab issues or chat. Use on transcripts, backlog, timeline, delivery date, status, orçamento, cotação, cronograma, enrich requirements — even if PM is unnamed. On "help" / "exemplos", list example prompts only. Do NOT use for coding, SDD requirements generation, or GitLab issue execution.
Define o sistema visual da marca além do logo. Use para criar direção de arte, paleta, tipografia, fotografia, ilustração e iconografia.
(NS) Consolidate delivered deltas into living domain specs under docs/specs/ — INDEX.md and per-domain markdown. Use after version closure when requirements, Approved code review, and execution-handoff exist; in ad-hoc mode when ns-coder (or the human) passes an Approved behavioral diff and docs/specs/ already exists; or in appearance mode from ns-proto-creator / ns-proto-visual-guide (no Code Review gate) for product-visible UX behavior. Updates specs incrementally; never overwrite unrelated content. Do NOT run Version/Ad-hoc before code review approval; appearance mode is the exception for prototype/visual handoff.
(NS) Guides correct usage of GitLab MCP tools for planning, milestones, issues, merge requests, delivery reports, and board sync. Use whenever the user mentions GitLab, MCP GitLab, create issues, start planning in GitLab, delivery report, issue comments, set_issue_labels, merge requests, or execution sync — even if they do not name this skill. Do NOT hand-craft issue payloads or skip confirmation gates. Do NOT use for non-GitLab project management.
(NS) Generate and adapt .gitlab-ci.yml for SaaS products with backend and frontend — test, build, E2E gate, deploy by branch. Use when the user asks for GitLab CI, pipeline setup, or CI/CD bootstrap for a monorepo product. Uses references/templates/gitlab-ci.template.yml as baseline. Out of scope for pure agent-runtime repos without backend+frontend layout.
(NS) Root-cause diagnosis from errors, logs, stack traces, failing tests, or CI — entry priority 4 when the user wants diagnosis WITHOUT implement ("why does X break?"). Use proactively on unclear test/CI failures if they have not asked to fix yet. Do NOT use for implement/fix (ns-coder), version scope (ns-spec-driven), GitLab ISSUE_URL execution, or pre-merge review (ns-reviewer).