「understand」の検索結果

Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use when the user says 'assess my codebase architecture', 'what direction should my codebase go', 'architecture compass', 'understand my architecture', 'audit architecture drift', 'architectural assessment', or 'help me understand what is wrong with my codebase'.

日本語の概要は準備中です。原文の説明を表示しています。

Parses and analyzes project vision to extract structured requirements. Use at project start to understand goals, scope, and constraints. Triggers on: analyze vision, parse project goals, understand requirements.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze an open-source project from What/Why perspective (not how-it's-implemented). Use when the user says "/analyze-oss", "분석해줘 이 오픈소스", "이 레포 뭐하는거야", "analyze this repo", "what does X do", "이거 왜 쓰는거야", "이 라이브러리 분석", provides a GitHub URL and wants understanding, or asks to deeply understand an OSS project's purpose, value, target users, and usage flow. Clones the repo to ~/opensource-analysis/<repo-name>/ (git pull if already exists), dispatches parallel subagents per analysis lens, then synthesizes a What/Why-focused report in chat. Supports optional user-specific follow-up questions.

日本語の概要は準備中です。原文の説明を表示しています。

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

日本語の概要は準備中です。原文の説明を表示しています。

The craft of designing icons that communicate instantly across cultures, contexts, and scales. Icon design bridges semiotics, cognitive psychology, and visual craft to create symbols that users understand without thinking. Great icons are invisible in the best way - they convey meaning so naturally that users never pause to decode them. This skill covers icon grid systems, optical alignment, stroke consistency, metaphor selection, scalability across sizes, SVG optimization, and icon set coherence. The best icon designers understand that icons are a visual language - each icon must speak the same dialect while carrying its own distinct meaning. Use when "icon, iconography, symbol, glyph, icon set, icon library, pictogram, svg icon, icon grid, icon pack, feather icons, lucide, phosphor, heroicons, icon system, icon style, icons, iconography, svg, symbols, glyphs, pictograms, ui-icons, icon-set, visual-design, design-system" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in navigating and manipulating git history. Covers finding bugs with bisect, understanding code evolution, recovering lost work, and rewriting history safely. Understands that git history is your time machine. Use when "git history, git bisect, find when bug introduced, recover deleted, rewrite history, git blame, lost commit, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive patterns for AI-powered document understanding including PDF parsing, OCR, invoice/receipt extraction, table extraction, multimodal RAG with vision models, and structured data output. Use when "document parsing, PDF extraction, OCR, invoice processing, receipt extraction, document understanding, LlamaParse, Unstructured, vision document, table extraction, structured output from PDF, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Audience Analysis workflow skill. Use this skill when the user needs Understand audience demographics, preferences, behavior patterns, and engagement quality across Facebook, Instagram, YouTube, and TikTok and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Audience Analysis workflow skill. Use this skill when the user needs Understand audience demographics, preferences, behavior patterns, and engagement quality across Facebook, Instagram, YouTube, and TikTok and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

antigravity-skill-orchestrator workflow skill. Use this skill when the user needs A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

antigravity-skill-orchestrator workflow skill. Use this skill when the user needs A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

arkcli +understand：基于 Responses API 的 12 个多模态专项理解配方，支持临时 API Key/Base URL/Endpoint 执行与无副作用 dry-run。用户只给 Endpoint 时先用 resources resolve；转写、抽取、字幕、定位等明确产出走本 skill，开放式对话走 +chat，生成走 +gen。

日本語の概要は準備中です。原文の説明を表示しています。

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze and optimize X (Twitter) posts for viral potential and reach using heuristics inspired by X's published open-source recommendation architecture. Use when user wants to: (1) Check if a post will go viral, (2) Score a tweet for engagement potential, (3) Optimize or rewrite a tweet for algorithmic reach, (4) Understand why a tweet underperformed, (5) Build audience in a specific niche. Triggers: "Check if this will go viral", "Make this post buzz", "Will this tweet perform well?", "Optimize my tweet", "How can I make this viral?", "rewrite this tweet", "improve my tweet engagement", "twitter algorithm", "tweet reach", "debug underperforming tweet", "バズるかチェックして", "Xでバズる投稿にして", "伸びるかチェックして", "この投稿を伸ばして", "投稿を改善して", "ツイートを最適化して"

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user wants intellectual understanding — learning how or why something works, not getting a task done or soliciting Claude's judgment. Trigger for: - Explicit learning requests: teach, explain, ELI5, walk me through, quiz me, flashcards, "I'm rusty on"; definitions ("what is X") - Terse concept names implying "help me understand this": "Galois theory," "transformers, from scratch" - Confusion signals: "won't stick," "keep mixing these up," "not getting it" - Learning-path questions: prerequisites, sequencing, what to study before X - Conceptual questions about mechanisms, causes, or dynamics Don't trigger for: - Tasks: coding, writing, calculation, translation, factual lookup, news updates - Personal troubleshooting; resource/textbook recommendations - Claude's evaluative verdict: opinion prompts ("do you think X", "settle this", "honest take", "is X dead / still taken seriously") and interpretive takes ("was X really as harsh as people say")

日本語の概要は準備中です。原文の説明を表示しています。

Select the right formative assessment technique for a specific learning moment, purpose, and age group. Use when choosing how to check understanding during, between, or after lessons.

日本語の概要は準備中です。原文の説明を表示しています。

Design a diagnostic hinge question that reveals whether students understand enough to move on. Use when planning key checkpoints mid-lesson during explicit or direct instruction.

日本語の概要は準備中です。原文の説明を表示しています。

Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do. Use when writing an explanation doc, conceptual guide, understanding/background doc, design rationale, or architecture explanation, or when asked how/why something works. Builds on the docs-style core writing principles.

日本語の概要は準備中です。原文の説明を表示しています。

Socratic tutor that teaches codebase understanding through questioning, challenges, and active recall. Invoke with /learn-codebase when onboarding to a new codebase or deepening understanding of existing code. Maintains a learning journal that tracks mastery and schedules reviews.

日本語の概要は準備中です。原文の説明を表示しています。

Expert knowledge of Behandlingsresultat (treatment result) domain in melosys-api. Use when: (1) Understanding result types and their meaning (FASTSATT_LOVVALGSLAND, MEDLEM_I_FOLKETRYGDEN, etc.), (2) Working with periods - Lovvalgsperiode, Medlemskapsperiode, Anmodningsperiode, Utpekingsperiode, (3) Debugging vedtak/decision metadata, criteria evaluation, or social insurance charges, (4) Understanding EU/EEA coordination logic and Article 16 exception handling, (5) Working with trygdeavgift (social insurance charge) calculations.

日本語の概要は準備中です。原文の説明を表示しています。