Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.
日本語の概要は準備中です。原文の説明を表示しています。
3,740 件 ・ 関連度順
概要と使いどころ
Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.
日本語の概要は準備中です。原文の説明を表示しています。
Response timing, acknowledgment, and making the interface feel alive. Every action deserves a response at the right speed. Use when designing interactions, evaluating responsiveness, or diagnosing why a product feels sluggish or dead.
日本語の概要は準備中です。原文の説明を表示しています。
Rank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.
日本語の概要は準備中です。原文の説明を表示しています。
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
日本語の概要は準備中です。原文の説明を表示しています。
Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.
日本語の概要は準備中です。原文の説明を表示しています。
Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data.
日本語の概要は準備中です。原文の説明を表示しています。
interview the user to design an agentic control loop (sensor, controller, actuator under disturbances) tailored to their codebase, then build it as locally-runnable components plus a scheduled coding-agent workflow
日本語の概要は準備中です。原文の説明を表示しています。
Master advanced Git techniques to maintain clean history, collaborate effectively, and recover from any situation with confidence.
日本語の概要は準備中です。原文の説明を表示しています。
Ask which skill or flow fits your situation. A route through AOS's skills for work that travels idea to ship, plus a catalogue of the available options for lookup. Use when unsure where to start, or when picking between overlapping choices.
日本語の概要は準備中です。原文の説明を表示しています。
Combines multi-agent brainstorming, the /grill-me slash command, and the 3 Core Godmodes (godmode-engineering, godmode-ui-ux, godmode-shipping) to force a comprehensive, multi-agent ideation and technical design workflow, ending in a plan-canvas review and a hand-off to /startcycle-graph. Use when the user asks to brainstorm, ideate, design, scope or sharpen a plan, idea or product, or when broad exploration before a build is the situation.
日本語の概要は準備中です。原文の説明を表示しています。
Linear multi-agent build pipeline with file hand-offs in production_artifacts/, run after /bdbrainstorm or /grill-me. This is the linear variant — no state.json, no repair loop, no dispatcher graph — distinct from startcycle-graph, which adds durable state and automated escalation. Use when an approved plan should be built, when the user types /startcycle or "run a startcycle", or when you pick a startcycle variant from the situation yourself (no user prompt needed).
日本語の概要は準備中です。原文の説明を表示しています。
LLM Agent engineering: pattern selection (12-mode matrix), data simulation, convergence iteration. Covers intent routing, function calling, ReAct, MCP, prompt chaining, guardrails, evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve SwiftUI runtime performance. Use when diagnosing slow rendering, janky scrolling, high CPU, memory usage, excessive view updates, layout thrash, body evaluation cost, identity churn, view lifetime issues, lazy loading, Instruments profiling guidance, and performance audit requests.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.
日本語の概要は準備中です。原文の説明を表示しています。
Helps detection engineers identify coverage blind spots in system command execution detection rules, evaluate bypass risks, and reduce false negatives. Strictly limited to system command execution rules; not applicable to browser credential theft or abnormal process creation without command semantics.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a job description, hiring post, or recruitment page for role requirements, evaluation criteria, keywords, risks, and resume or cover letter angles. Use when the user provides a JD URL/text, asks what a company is looking for, wants JD-resume gap analysis, or needs inputs for a tailored cover letter. 한국어 요청도 포함합니다 - 채용공고 분석, 공고 분석, JD 분석, 직무기술서 분석, 자격요건, 우대사항, 이 공고 뭘 원하는지, 공고랑 내 경력 비교.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for using completers — TokenCompleter and MessageCompleter for text generation during RL rollouts and evaluation. Use when the user asks about generating text, completing messages, or using completers in RL environments.
日本語の概要は準備中です。原文の説明を表示しています。
Analytical methodology skill for intelligence-grade research. Covers cognitive security, logical fallacy detection, source epistemology, and probability discipline. Load when evaluating sources, building analytical assessments, or detecting manipulation in information.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance checking, or App Store submission readiness.
日本語の概要は準備中です。原文の説明を表示しています。
No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power
日本語の概要は準備中です。原文の説明を表示しています。
Expert in designing effective prompts for LLM-powered applications. Masters prompt structure, context management, output formatting, and prompt evaluation. Use when: prompt engineering, system prompt, few-shot, chain of thought, prompt design.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "perform vulnerability scanning", "scan networks for open ports", "assess web application security", "scan wireless networks", "detect malware", "check cloud security", or "evaluate system compliance". It provides comprehensive guidance on security scanning tools and methodologies.
日本語の概要は準備中です。原文の説明を表示しています。