- Skills
- 12
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
NAPHAT EM-ONG 的 Skills 12
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
task-observer
Monitors task execution for skill improvement opportunities: logs patterns, user corrections and methodology worth preserving to the workspace, turns them into skill updates in a weekly review, and flags repeating work as new skills. Use during ANY multi-step task, agentic workflow, or work session. Also triggers in post-task feedback discussions and when the user mentions skill observations, the observation log, or skill taxonomy. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: invoke this skill before the FIRST tool call of any session and before writing or proposing a plan — any turn that will involve a tool call counts. This sentence is the session-start trigger and the only activation layer that survives an unreachable config file; pair it with a CLAUDE.md instruction or a session-start hook (references/environments.md). A subagent dispatched by a session already running it does not run it: it writes nothing and puts its findings in its report.
superpowers-ponytail
Combines 'using-superpowers' and 'ponytail'. Enforces disciplined skill invocation BEFORE any response or action (brainstorming, systematic-debugging, process skills first) while strictly executing with Ponytail's ruthless simplicity (YAGNI, minimal diff, stdlib/native first, no boilerplate, shortest working path). Use on ANY coding, debugging, or architecture task where you want both strict skill-first workflow and lazy minimal-diff execution. Also triggers on /superpowers-ponytail, /ponytail-superpowers, "ponytail superpowers", "lazy superpowers", or whenever combining disciplined process with minimalist code.
stress-tested-architecture
Combines 'brainstorming' and 'grilling'. Interactive design, RFC, and system architecture workflow that couples collaborative exploration with adversarial stress-testing. Features Three-Path Classification (Spike, Bounded, Architectural), a branching Design Tree, structured Grilling Rounds (The Frontier) with recommended answers, and rigorous scrutiny on failure modes, scale, and trade-offs before locking specifications. Triggers on /stress-tested-architecture, /grill-architecture, "design architecture", "brainstorm and grill", "stress test plan", or "system design RFC".
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
precision-diagnostics
Combines 'systematic-debugging' and 'diagnosing-bugs'. Strict multi-phase root-cause diagnosis protocol for hard bugs, intermittent failures, test breakages, and performance regressions. Enforces building a tight deterministic feedback loop (repro), multi-boundary instrumentation, ranked falsifiable hypotheses, and minimal root-cause fixes with regression tests before any code edits. Triggers on /precision-diagnostics, /diagnose, "diagnose bug", "debug hard bug", "systematic debug", or any persistent/intermittent software failure.
pptx-generator
Generate, edit, and read PowerPoint presentations. Create from scratch with PptxGenJS (cover, TOC, content, section divider, summary slides), edit existing PPTX via XML workflows, or extract text with markitdown. Triggers: PPT, PPTX, PowerPoint, presentation, slide, deck, slides.
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
office-mcp
MCP server with 39 tools for Word, Excel, PowerPoint, PDF, OCR operations
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler. Based on Wikipedia's "Signs of AI writing."
humanizer-th
แก้ข้อความภาษาไทยที่ "ดูเหมือน AI เขียน" ให้อ่านเหมือนคนเขียน โดยไม่เปลี่ยนสาระและไม่เพิ่มข้อมูลที่ไม่มีในต้นฉบับ ครอบคลุม 26 รูปแบบการเขียนที่ต้องระวัง (ไม่ใช่แค่ X แต่เป็น Y, ปิดท้ายบรรทัดเดียว, คำพูดที่ฟังดูลึกลับ, การออกตัวก่อนเริ่ม, การเถียงกับคนที่ไม่มีอยู่, การยกสาม, ขีดกลางทุกช่วง, คำขยายที่ซ้อน, การเพิ่มความสำคัญเกินจริง, ศัพท์อังกฤษที่ไม่จำเป็น, บรรทัดปิดด้วยคำถาม, ตัวหนาแต่งแต่ง, ข้อความค้างจากแชทบอท, การอธิบายเรื่องเอง) และอีก 10 รูปแบบเฉพาะภาษาไทย (ใช้ "ถูก/โดน" กับเรื่องบวก, ทำการ + การซ้อน, ครับ/ค่ะ ไม่ตรงผู้พูด, คำเชื่อมทางการที่ขึ้นต้นทุกประโยค, สรรพนามฟุ่มเฟือย, เว้นวรรคผิด, ๆ ๏ ฯ ผิดตำแหน่ง, ข้อความที่ไร้ความเป็นคน) พร้อมคู่มือว่าเอกสารแต่ละแบบควรเขียนอย่างไร และกฎอักขรวิธีภาษาไทย ใช้ทุกครั้งที่ผู้ใช้ขอ "ทำให้เป็นธรรมชาติ", "ลดความเป็น AI", "แก้บทความ", "ปรับให้ดูเหมือนคนเขียน", "ตรวจงานที่เขียนด้วย AI", "เขียนใหม่ให้เป็นธรรมชาติ", "ปรับภาษาไทยให้ดูมืออาชีพ" หรือส่งข้อความภาษาไทยมาให้ปรับแต่ง แม้ผู้ใช้ไม่ได้เอ่ยชื่อสกิล
archify
Create validated architecture, workflow, sequence, data-flow, lifecycle/state, ERD, class, tree, timeline, and waterfall diagrams as explorable standalone HTML with dark/light themes, motion and image/SVG/WebM export. Accept requirements or Mermaid; inspect repository evidence for code-backed diagrams. Use when visualizing systems, API calls, pipelines, schemas, histories, timings, or everyday steps, parts, relationships and states. Also turn an answer into a one-page explainer, with the conclusion first, structured panels, native diagrams and charts, when the user asks for a page, an explainer or an answer to share (做成一页, 用页面讲), or proactively when the user's rules opt in with an [archify explainer: ...] line. Not for dashboards.