Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium.
日本語の概要は準備中です。原文の説明を表示しています。
7,665 件 ・ 関連度順
概要と使いどころ
Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium.
日本語の概要は準備中です。原文の説明を表示しています。
Before improving anything, show the spread of what can concretely be done on this specific input — a short menu of 3-5 interventions from lightest to heaviest touch, then wait for the user to pick. Domain-agnostic; works on any material the user hands over. Trigger when the user says "spread", "show me my options", "what can you do with this", or asks to improve or fix something without specifying how. Do NOT trigger when the user has already named a specific fix — then just do the fix.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a ready-to-paste social post kit for an app, tool, or project launch or update — "make social posts", "launch posts", "post kit", "prep socials", "promote this". Produces one Markdown file with finished posts for X, Reddit, Instagram, LinkedIn, Threads, and short-form video, plus a pre-post checklist. Pull real facts from the project (repo, release, what it does, OS, links).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to create, add, convert, publish, or deploy a blog post from a draft, notes, Markdown, outline, or topic. Turns a draft into a complete, SEO/GEO-optimized post wired into the site (template, blog index, sitemap, routing) with QA and deploy. Framework-agnostic — discover the project's own conventions first.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user adds a project to the workspace, opens an unfamiliar repo, asks "what is this project", "explain this codebase", or invokes explain-new-project. Explores a newly opened workspace project and writes a plain-language report for a self-taught, non-technical user—quick start (what it is + how to run) first, then optional depth—and always saves PROJECT_GUIDE.md in the project root.
日本語の概要は準備中です。原文の説明を表示しています。
创建 lark-cli 的自定义 Skill。当用户需要把飞书 API 操作封装成可复用的 Skill(包装原子 API 或编排多步流程)时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.
日本語の概要は準備中です。原文の説明を表示しています。
Track work as GitHub issues in this monorepo — create epics + child/sub-issues, label them consistently by package/app, and tie them into the commit workflow. Use when planning a feature, breaking work into tasks, or asked to "track this in GitHub", "make issues", "set up tracking".
日本語の概要は準備中です。原文の説明を表示しています。
Activates a structured decorator framework that modifies how Claude reasons, responds, and formats output. Trigger this skill whenever a prompt contains one or more markers prefixed with +++, such as +++Reasoning, +++StepByStep, +++Tone(style=formal), or any other +++ marker, regardless of what follows in the prompt. Also trigger when the user asks to activate, list, or clear decorators, references the prompt decorator framework, or uses phrases like "use decorator", "apply +++", or "what decorators are available". This skill must be active for any +++ marker to take effect.
日本語の概要は準備中です。原文の説明を表示しています。
ユーザーが言語化できない「何を入力し、何をどう出力してほしいか」を深掘って intent_contract と 5 軸ヒアリングシートを再現性高く埋めたいとき、run-skill-intake から phase 4 として呼ばれて sheet.md/sheet.json/interview.json を生成したいときに使う。
進行中のskill intakeのphaseと5軸を確認したいとき、visualとNotion公開状態をread-onlyで確認したいときに使う。
First-principles strategy — strip away conventional assumptions and find the theoretical maximum for your business. Three modes. Diagnostic mode runs a full session (45+ min) to define your theoretical maximum, map the gap honestly, classify constraints, invert for failure modes, set strategic intent, and work backwards to your first intervention. Review mode (15-20 min) checks whether your theoretical maximum has shifted, whether the gap has changed, and whether you're still climbing the right peak. Alert mode defines constraint-shift, peak-shift, and local-peak triggers that tell you when to reassess. Use when someone is stuck optimising incrementally, when conventional wisdom is driving strategy, when a new technology or regulation changes what's physically possible, or when you suspect the business is climbing a local peak. Integrates with company-context.md. Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
A deliberately leaky demo skill used to show what skill-sanitizer catches before you publish. Do not ship this.
日本語の概要は準備中です。原文の説明を表示しています。
Set up AI Runway on AKS — from bare cluster to running model. Covers cluster verification, controller install, GPU assessment, provider setup, and first deployment. WHEN: "setup AI Runway", "onboard AKS cluster", "install AI Runway", "airunway setup", "deploy model to AKS"...
日本語の概要は準備中です。原文の説明を表示しています。
Convert tasks from tasks.md into GitHub issues. Use after task breakdown to track work items in GitHub project management.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when developing code using Test-Driven Development (TDD) methodology. Use this skill when the user wants to write tests first before implementation, needs guidance on the red-green-refactor cycle, or explicitly requests TDD-style development. Triggers include requests like "develop this feature using TDD", "write tests first", "help me with test-driven development", or "implement this following TDD practices". The skill guides through writing failing tests, implementing minimal code to pass, and refactoring while maintaining test coverage.
日本語の概要は準備中です。原文の説明を表示しています。
CVP(Cost-Volume-Profit)分析・損益分岐点分析スキル。固定費・変動費の構造分析、 限界利益率の算出、損益分岐点売上高/数量の計算、安全余裕率の評価、 目標利益達成に必要な売上高のシミュレーションを行う。多品目分析にも対応。 Use when: 損益分岐点を知りたいとき、新規事業や価格変更の採算シミュレーション、 固定費削減・変動費率改善の効果試算、What-if分析に使用。 Triggers: "損益分岐点", "CVP", "break-even", "限界利益", "contribution margin", "安全余裕率", "margin of safety", "固変分解", "変動費率"
This skill should be used when creating comprehensive project plans for system development or implementation projects. Use this skill when you need to create Project Charters, Project Plans, WBS, Gantt Charts, RACI matrices, Risk analysis, or other PMBOK-aligned project management artifacts. Outputs are in Markdown format with Mermaid diagrams for visualizations. Leverages comprehensive PM knowledge base in references/ directory (544KB, 11 files) including PMBOK standards, Software/SaaS best practices, IT industry guidance, and specialized PM methodologies.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for critical code review that focuses on whether the code actually works correctly and achieves the expected results - not just whether it matches a design document. This skill assumes designs can be wrong, finds bugs the design didn't anticipate, and verifies end-to-end correctness. Triggers include "critical code review", "deep code review", "verify this implementation works", "find bugs in this code", or reviewing implementation against requirements. NOTE - Security review is OUT OF SCOPE; use a dedicated security review skill for that purpose.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when creating professional presentation materials, slide decks, or proposal documents following FUJISOFT America's corporate template standards. Triggers include requests like "create a presentation", "make slides", "prepare proposal materials", "FUJISOFT template", or when MARP-format Markdown presentations are needed with consistent corporate branding. The skill provides a complete MARP template with CSS styling, visual design components, and quality assurance workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Compose professional internal emails for coordination tasks like vendor quote requests, task delegation, and follow-up communications. Generates bilingual (JA/EN) email drafts with proper business tone. Use when user needs to draft internal emails for vendor RFQ forwarding, quote compilation requests, status updates, or task delegation.
日本語の概要は準備中です。原文の説明を表示しています。
ego-browser (ego-lite) is a Chromium-based browser that gives AI agents a CLI-accessible Node.js runtime for driving a real browser. Use this skill whenever the user needs to interact with a website opening pages, filling forms, clicking buttons, taking screenshots, extracting page data, testing web apps, logging into sites, automating browser operations, or any other browser automation task. Triggers include requests to "open a website", "visit a URL", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "extract content from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also used for exploratory testing, dogfooding, QA, bug hunting, or reviewing app quality. Prefer ego-browser over any built-in browser automation, web fetch, or other web tools.
日本語の概要は準備中です。原文の説明を表示しています。
Split user stories into smaller, independently deliverable slices using the SPIDR method (Spike, Path, Interface, Data, Rules). Use this skill whenever the user asks to split a story, break down work, slice a story, asks "can this be split", mentions "SPIDR", says "story splitting", or wants to decompose a large ticket into smaller pieces. Also trigger when a user presents a story that seems too large for a single sprint and asks for help sizing or scoping it.
日本語の概要は準備中です。原文の説明を表示しています。
Metakognitive Injektoren und Selbstgesprächs-Strategien (Self-Talk, Metacognitive Auditing, Evaluator Hooks, Pre-Flight Checklists, State Persistence & Personas). Integriert Aktive Informationssuche (Systemgedächtnis Gardener & USMC), Rehearsal (Aktives Abrufen & Wiedergeben), Baddeleys Arbeitsgedächtnis (State + Hooks), Miyake Exekutivfunktionen sowie CBT/ACT therapeutische Strategien.
日本語の概要は準備中です。原文の説明を表示しています。