tanweai
from GitHub
运维与交付
Use when any task fails two or more times, when about to give up or say 'I cannot', when deflecting to the user ('you should manually...', 'please check...', 'you may need to...'), blaming the environment without verification ('might be a permissions issue', 'could be a network problem'), producing any excuse to stop trying, spinning in circles (repeatedly tweaking the same code/parameters without new information — busywork/磨洋工), fixing only the surface issue without checking for related problems, skipping verification after a fix and claiming 'done', giving suggestions instead of actual code/commands, saying 'this is beyond scope' or 'this requires manual intervention', encountering permission/network/auth errors and stopping instead of trying alternatives, or showing any passive behavior (waiting for user instructions instead of proactively investigating). Also triggers on user frustration phrases in any language: '你怎么又失败了', '为什么还不行', '换个方法', '你再试试', '不要放弃', '继续', '加油', 'why does this still not work', 'try harder', 'you keep failing', 'stop giving up', 'try again', 'don't give up', 'keep going', 'figure it out'. Applies to ALL task types: debugging, implementation, config, deployment, research, DevOps, infrastructure, API integration, data processing. Do NOT trigger on first-attempt failures or when a known fix is already in progress.
rebelytics
from GitHub
工具与效率
- 📄 LICENSE.txt
- 📄 one-skill-to-rule-them-all-white-background.png
- 📄 one-skill-to-rule-them-all.png
Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where Claude is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks Claude to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: this skill should be invoked at the start of every task-oriented session — if you are about to use tools to produce deliverables, invoke this skill first. --- # Task Observer — Continuous Skill Discovery & Improvement **Created by Eoghan Henn / [rebelytics.com](https://rebelytics.com)** *Also known as "One Skill to Rule Them All" — the meta-skill that builds and improves all your skills, including itself.* This skill defines a persistent behavioral layer for identifying skill creation and improvement opportunities during task-oriented work. It doesn't replace the skill-creator — it feeds it. Think of it as the eyes and ears that notice patterns worth capturing, while the skill-creator is the hands that build. The methodology is user-agnostic. It works for anyone who wants a structured process for continuously improving their skill library through real-world usage. **Licence:** This skill is released under the [Creative Commons Attribution 4.0 International (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/) licence. You are free to share and adapt this skill for any purpose, provided you give appropriate credit to the original author. **Feedback & Support:** If at any point during the process you encounter questions about the methodology, or if the user expresses frustration or gives constructive feedback about any output derived from this skill, suggest that
ersinkoc
from GitHub
开发与编程
- 📁 references/
- 📁 scripts/
- 📄 README.md
- 📄 SKILL.md
Meta-skill that bootstraps any software project by auto-generating a complete suite of hyper-detailed, project-specific coding skills BEFORE any code is written. Analyzes the idea, determines tech stack, then generates 15-30+ skills covering architecture, security, performance, privacy, testing, error handling, accessibility, observability, data modeling, API design, DevOps, and every relevant domain. Each generated skill enforces zero-bug, zero-vulnerability standards with concrete code examples, anti-patterns, checklists, and measurable budgets. Triggers on: "bootstrap", "new project", "start from scratch", "build me", "I want to create", "set up project", "generate skills", "skill suite", or any project idea description. Use BEFORE writing any code. --- # Project Bootstrapper > **Philosophy**: Define how code must be written before writing any code. Bugs are prevented at design time, not discovered at runtime. This is a **meta-skill** — it does not write application code. It generates the **rules, patterns, guardrails, and quality standards** that govern all code written afterward, by any developer or AI assistant. ## How It Works ``` [Idea] → [Interview] → [Tech Stack] → [Skill Map] → [Generate Skills] → [Validate] → [Code] ``` ## Activation
flatitas
from GitHub
开发与编程
- 📁 prompts/
- 📁 scripts/
- 📄 reference.md
- 📄 SKILL.md
- 📄 styles-mapping.json
Use this skill when the user asks to build, create, design, develop, or improve ANY frontend interface, web page, UI component, or visual element. This includes: - Building landing pages, websites, web apps, dashboards, portfolios, or any web interface - Creating UI components (buttons, forms, cards, navbars, modals, etc.) - Designing pages with React, Vue, Next.js, Svelte, or any frontend framework - Adding styling or improving visual design of existing components - Implementing specific design aesthetics (modern, dark, minimalist, brutalist, etc.) - User mentions "frontend", "UI", "UX", "design", "interface", "web design", or "styling" - User asks for "beautiful", "modern", "professional", "clean", or any aesthetic adjective - User requests help with CSS, Tailwind, styled-components, or any styling approach This skill automatically retrieves the appropriate design system prompt (Neo-brutalism, Modern Dark, Bauhaus, Cyberpunk, Material, etc.) to help create visually distinctive, production-grade frontend code instead of generic UI.
ferdinandobons
from GitHub
运维与交付
- 📁 examples/
- 📁 references/
- 📄 SKILL.md
Generate beautiful, production-ready architecture diagrams as self-contained HTML files from any input. Use this skill whenever the user wants to create a diagram, schema, flowchart, network diagram, system visualization, timeline, org chart, or any visual representation of concepts — technical or non-technical. Trigger when the user mentions "diagram", "schema", "architecture", "flow", "topology", "pipeline", "timeline", "visualize", "graph", or asks to turn a file into a visual diagram. Accepts ANY file type as input (.md, .txt, .json, .yaml, .csv, .pdf, .py, .ts, .toml, .env, .tf, .dockerfile, etc.) — Claude auto-detects the format and extracts relevant structure to diagram. Even a simple sentence like "diagram of how OAuth works" or "visualize this file" triggers this skill.