← all publishers

wolf123450

@wolf123450 source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Playwright Testing · wolf123450

   Use when writing, running, or debugging Playwright tests against a web application (not Tauri/desktop apps — see tauri-playwright for that), or when driving a live browser to verify or demo a feature. Covers locator strategy, waiting, network mocking, debugging failures, and delegating test runs to a subagent so verbose output stays out of the main session.
   0 installs
2. ▌
   Feature Maturity · wolf123450

   Shared vocabulary for describing how done a feature or piece of code actually is. Use when scoping work up front ("build this to Functional"), before declaring any implementation task complete (self-report a maturity reading, don't just say "done"), when auditing existing code's maturity, or when the user and Claude disagree about whether something is Finished/Polished/Hardened/etc. and need to argue from shared criteria instead of vibes.
   0 installs
3. ▌
   Claude Code Statusline · wolf123450 bundle

   Use when the user wants to set up, install, or replicate a Claude Code status line showing model name, session token usage, context-window percentage, and 5h/7-day rate-limit usage — including on a new machine or in a fresh environment.
   0 installs
4. ▌
   Claude Code Token Optimization · wolf123450

   Use when the user wants to cut Claude Code token/context spend, complains sessions are getting expensive, or asks to set up session-hygiene and subagent-delegation discipline — including replicating this setup on a new machine or in a fresh environment.
   0 installs
5. ▌
   Godot Setup · wolf123450 bundle

   Use when setting up a new Godot 4.x C#/.NET project for Claude Code agentic development, or bootstrapping MCP servers, local docs indexing, third-party skill curation, custom skills, subagents, and hooks for an existing Godot project. Not for API reference lookups — see the docs-layer setup for that.
   0 installs
6. ▌
   Demoing Work · wolf123450

   Use when implementation work is complete and automated checks (tests, verify, verification-before-completion) pass, before telling the user the work is done. Walks the user through the golden path and relevant edge cases live, then gates completion on the user's explicit confirmation rather than self-declaring the work finished. Use for both UI-facing changes (demo live in the app) and non-UI changes (narrated CLI/API walkthrough).
   0 installs
7. ▌
   Game Catchup · wolf123450

   Generate a structured "what you missed" recap for a game the user hasn't played in a while. Use this skill whenever the user says they haven't played a game recently and wants to catch up, asks what's changed or been added to a game since a specific date, mentions they're "returning" to a game, or asks for a summary of updates/patches for any game title. Trigger even when the request is casual ("what's new in X since I last played?", "can you catch me up on Y?", "I stopped playing Z in [month], what did I miss?"). Also trigger proactively if the user mentions they used to play a game but stopped — a catchup offer is appropriate.
   0 installs