「hands-on」の検索結果

Applies the pragmatic, financially-grounded reasoning of Marian Ilitch (co-founder of Little Caesars Pizza). Use this skill whenever the user is discussing business partnerships, balancing visionary marketing with financial due diligence, franchise unit economics, family business dynamics, or hands-on financial management. Trigger this when users face trade-offs between rapid growth and profitability, need to enforce unit-level accountability, or are paralyzed by the fear of making mistakes. Apply her principles to ground lofty ideas in tactile, common-sense financial reality.

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

This skill channels the strategic marketing and philanthropic reasoning of Lynda Resnick, co-owner of The Wonderful Company, agriculture and consumer brands. Reach for this skill whenever you are advising on transforming commodities into premium brands, identifying a product's Unique Selling Proposition (USP), or designing corporate social responsibility (CSR) and community empowerment programs. Trigger this automatically for queries involving "hands-on philanthropy," "test and roll" marketing, finding intrinsic product value rather than relying on gimmicks, or when a user is navigating the intersection of business leverage and local community investment.

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

Implement, build, create, or add any feature, endpoint, page, component, or functionality. Use this skill whenever the user asks you to write new code or make code changes — whether it's adding an API endpoint, building a UI page, creating an export feature, wiring up a webhook, implementing a search/filter, or any other hands-on coding task. This is the default skill for all 'build this', 'add this', 'create this', 'wire up', 'implement' requests. Covers the full cycle: clarify requirements, plan if needed, write code, verify, and review. Do NOT use for pure research, debugging, documentation, or explanation — only when the user wants working code delivered.

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

Design a Montessori three-period lesson for introducing concepts through concrete materials and naming. Use when teaching vocabulary, classifications, or concepts through hands-on materials.

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

Tutorial patterns for documentation - learning-oriented guides that teach through guided doing. Use when writing a tutorial, learning guide, getting-started or onboarding guide, beginner/introductory guide, or any learn-by-doing hands-on guide. Builds on the docs-style core writing principles.

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

Experience-based and environment-based learning design drawn from Dewey and Montessori. Covers Dewey's criterion of continuity and interaction, the reflective-thinking cycle, Montessori's prepared environment, sensitive periods, child-led inquiry, the role of self-correcting materials, project-based learning, and the relationship between autonomy and discipline. Use when designing hands-on activities, arranging learning spaces, integrating classroom work with real experience, or evaluating whether a lesson is genuinely experiential versus merely "activity-based."

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

Transition from a hands-on "bricklayer" to a high-level "architect" by managing a fleet of autonomous AI agents. Use this when you need to scale engineering output with a small team, handle repetitive migrations/bug fixes, or onboard engineers to complex legacy codebases.

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

Cultivate edible and medicinal mushrooms from spawn through fruiting. Covers substrate preparation, inoculation methods, incubation conditions, fruiting chamber management, harvest timing, and successive flushes for oyster, shiitake, lion's mane, and other commonly cultivated species. Use when growing edible mushrooms without the risks of wild foraging, when a reliable supply of fresh culinary or medicinal mushrooms is needed, or when exploring mycelial ecology through hands-on cultivation practice.

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

Use for hands-on repository work when a quiet, risk-scaled engineering method can improve design, implementation, debugging, review, delegation, workspace lifecycle, or verification. Keep clear local changes direct, preserve the complete requested outcome, and add method only where risk or uncertainty justifies it. Do not use for general technical explanations, simple file lookup, casual discussion, or non-engineering writing.

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

Use for hands-on Pulumi CLI work: running deployments, fixing broken stacks, and managing infrastructure state. Handles: recovering from stuck or interrupted `pulumi up` with pending operations, cleaning orphaned resources from state after out-of-band cloud deletions, protecting critical resources from accidental `pulumi destroy`, moving resources between stacks without recreating them, targeting specific resources during deployment, migrating between backends (local file to Pulumi Cloud, S3), stack lifecycle management, state export/import/repair, CI/CD pipeline setup, and importing existing cloud resources. Use this skill — not the language-specific Pulumi skills — whenever the user's question is about operating, troubleshooting, or recovering Pulumi infrastructure rather than writing program code.

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

Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE after completing any significant implementation work. Triggers: 'review work', 'review my work', 'review changes', 'QA my work', 'verify implementation', 'check my work', 'validate changes', 'post-implementation review'.

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

One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.

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

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.

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

When the user wants to create step-by-step technical tutorials, quickstarts, or code walkthroughs. Trigger phrases include "tutorial," "quickstart," "getting started guide," "walkthrough," "step by step," "how to guide," "hands-on guide," or "code tutorial."

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

Knowledge base from the GAO Agile Assessment Guide (GAO-24-105506, 2023). Use for assessing and managing Agile software development in federal programs: the Agile Manifesto and framework family (Scrum, Kanban, XP, SAFe, DA, DSDM, Lean, DevOps); the three adoption perspectives (team dynamics, program operations, organization environment); requirements decomposition (epics, features, user stories, INVEST, MoSCoW, definition of done); Agile-aware federal contracting (FAR, modular contracting, SOO/PWS/SOW, product owner vs. COR); program monitoring and control (WBS, cost, schedule, EVM at the feature level); Agile metrics (velocity, lead/cycle time, CFD, burn charts); and the auditor's key-question bank. Oversight- and acquisition-oriented: it tells you how to *assess and govern* Agile programs, not how to code. Thin on hands-on engineering practice, deep cost/schedule checklists (see gao-cost, gao-schedule), and any non-US-federal context.

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

Find live third-party GitHub issues and discussions on topics where you have real hands-on experience and artifacts, then reply with that experience to build reputation. Use when asked to answer people about your work, find threads matching your expertise, or reply with evidence from your own setup.

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

Use when the user provides a URL from AMD / ROCm official sources (github.com/AMD/*, github.com/ROCm/*, github.com/ROCmSoftwarePlatform/*, rocm.docs.amd.com, amd.com/…/rocm, gpuopen.com). Prefer this over generic GitHub for official ROCm URLs. Generates a hands-on tutorial-following project with no collaborator roles — only the user and the Instructor.

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

Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials, or concept explanations.

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