36건(harperreed의 저장소) · 인기순
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Native macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces. Use when asked to profile, attach, record, or analyze Instruments .trace files, find hotspots, or optimize native app performance without opening Instruments UI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
uv workflows for Python — dependencies, virtualenvs, PEP 723 scripts, Python version management, CI, and Docker. Use when working on Python packaging/deps/tooling, writing GitHub Actions for Python projects, or building Docker images for Python apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when someone wants to launch a content brand from scratch on any platform. Triggers on "launch a channel", "start a YouTube channel", "build a podcast", "start a newsletter", "content brand", "creator launchpad", "build my audience", "start creating content", "grow on TikTok", "start a blog".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a pipeline DOT file has passed structural validation but may still have flow inefficiencies, spec fidelity gaps, or information loss in prompts. Use after dotfile-audit or dotfile-from-spec when you want to deeply verify a pipeline captures everything from the original spec. Use when prompts might be missing critical domain rules, data models, or invariants.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to import, sync, or add Granola meeting notes into the Obsidian vault. Triggers on "meeting notes", "Granola", "import meetings", "add notes from this week", or any request to move meeting content into Obsidian.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Semantic memory and context - store and retrieve information with embeddings for similarity search. Use for long-term memory, context recall, and knowledge persistence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user explicitly says "Nothing style", "Nothing design", "/nothing-design", or directly asks to use/apply the Nothing design system. NEVER trigger automatically for generic UI or design tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a completed Shell scenario planning exercise needs to be converted into a TikTok script. Triggers when user says "make a tiktok", "tiktok script", "generate tiktok", or "content from scenario". Requires a completed scenario with narratives, findings, and worldview integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when someone has a business problem, strategic question, or founder challenge they need to think through clearly. Triggers on "I'm stuck on", "should I", "what's wrong with my", "diagnose", "strategy problem", "business problem", "founder problem", "help me think through". Runs structured consulting-style diagnostic lenses to produce a comprehensive analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when processing, summarizing, or extracting insights from meeting notes in the Obsidian vault. Triggers on "summarize meetings", "process meetings", "meeting summaries", "extract from meetings", "meeting insights".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when someone wants to build, refine, or audit their personal brand positioning across professional platforms. Triggers on "personal brand", "brand positioning", "brand voice", "how should I position myself", "professional identity", "LinkedIn presence", "build my brand".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you have a spec, design doc, structured plan, or prompt_plan and need to generate a pipeline Graphviz DOT file for headless autonomous building. The agent reads the spec, extracts build pipeline phases, determines tech stack, asks about human gates and model preferences, generates a validated DOT digraph with rich self-contained prompts, and saves it to the project root. Handles any language or framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when preparing a release, tagging a version, or when user says "release", "tag", "ship it", "push to production" - ensures all release artifacts are verified before tagging to avoid the retag-four-times failure pattern
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you want to build a project but don't have a spec yet and need to brainstorm the idea into a design doc structured for pipeline DOT generation. Use when starting from a vague idea, project concept, or feature request that needs to become a headless autonomous build pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to check on agents, manage their fleet, babysit panes, see what needs attention, get a status report, or when they say "check on my agents", "what needs action", "fleet status", "babysit", "brief me". Requires the control MCP server to be registered and the daemon running.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing marketing, messaging, offers, funnels, or content strategy. Triggers on "audit my marketing", "review my landing page", "improve my funnel", "content strategy review", "messaging review", "offer feedback", "marketing checkup", "why isn't my marketing working", "audit my brand". Works at any budget or company size.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.