「meaning」の検索結果

great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.

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

Extract reusable patterns from non-trivial work in the is-kit repository and store them as project knowledge. Use after meaningful API design, type-system work, debugging, or compatibility discoveries.

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

Implements behavior changes with a test-first red-green-refactor loop: write one meaningful failing test, watch it fail for the intended reason, make the smallest change, then refactor while green. Use for new behavior, bug fixes, refactors with preserved contracts, and regression tests. Not required for disposable prototypes, generated files, or documentation-only edits.

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

Implementing CSS/JS animations for hover effects, loading states, modal transitions, and gesture interactions. Use for meaningful motion, interaction feedback, or performance-safe animation.

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

Turns implementation work into working code, reviewed and verified. Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts. Skip obvious, low-risk mechanical maintenance such as small ignore-file, typo-only, formatting-only, or configuration-hygiene edits. Explicit BMAD requests always qualify. Do not volunteer for user-directed interactive edits or version-control operations that only record existing work.

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

Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.

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

Translate a confirmed mini-program product specification or bounded feature into an implementable architecture covering modules, pages, components, services, canonical state sources, data models, interfaces, permissions, failures, caching, concurrency, idempotency, migration, rollback, external dependencies, and architecture decision records. Use when users ask how to structure a mini program, design data or APIs, divide frontend and cloud responsibilities, evolve an existing system safely, or prepare implementation after product semantics are stable. Preserves product meaning, current repository constraints, user-owned changes, and verifiable acceptance behavior rather than redesigning the product for technical convenience.

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

Satori is a clinically informed wisdom companion for navigating the inner life — emotions, meaning, grief, purpose, relationship, identity, and the questions that don't resolve easily. Activate when someone is processing something difficult, wrestling with a life question, seeking perspective, or simply needs to think alongside someone who won't rush them toward an answer. Also activate when someone uses language like "I've been struggling with," "I don't know what to do," or "I need to figure out" — or any emotionally charged framing. When in doubt, activate. Draws from Taoism, Buddhism, Stoicism, Christianity, Sufi wisdom, Hindu philosophy, Confucian ethics, and African thought, alongside modern psychology, neuroscience, and trauma-informed frameworks (IFS, DBT, CFT, Schema Therapy, Somatic). Uses Motivational Interviewing, Voss tactical empathy, McAdams Life Story, and Singer Self-Defining Memory — woven naturally, not mechanically.

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

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.

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

Define semantic type detectors in detectors.js for auto-detecting column data meaning

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

Few semantic colours, each meaning one thing, and errors with a way forward. Use when designing status indicators, validation, alerts or error states.

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

Vocabulary learning strategies and retention science for any language -- frequency-based word selection, spaced repetition systems (Ebbinghaus forgetting curve, Leitner system, SM-2 algorithm), cognate exploitation, word family networks, context-based learning, collocations, depth of word knowledge (form, meaning, use), reading progression from controlled to authentic texts, and productive vs. receptive vocabulary thresholds. Use when building vocabulary plans, optimizing review schedules, selecting learning materials, or diagnosing vocabulary gaps.

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

Grammar and syntactic structures across human languages -- word order typology (SVO, SOV, VSO, VOS, OVS, OSV), morphological systems (isolating, agglutinative, fusional, polysynthetic), agreement patterns (gender, number, case, person), phrase structure, clause embedding, and cross-linguistic universals. Covers constituent analysis, dependency vs. constituency grammars, grammatical relations (subject, object, oblique), ergativity vs. accusativity, tense-aspect-mood systems, and how grammar encodes meaning differently across language families. Use when analyzing sentence structure, comparing grammar systems, teaching grammatical concepts, or understanding why a learner makes transfer errors from their L1.

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

Use when orchestration or planning agents are producing task plans, task prompts, or TASK.md instructions that must be unambiguous, verifiable, and resistant to hallucination. Applies CLEAR (Concise, Logical, Explicit, Adaptive, Reflective) to structure and write agent task prompts, then adds CoVe (Chain of Verification) checks where accuracy risk is meaningful. Activates on draft task prompts, swarm plans, migration tasks, and multi-step plans requiring independently executable steps.

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

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

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

Analyze changes and create a meaningful commit with agent authorship. Internal skill for evolve_loop.

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

Use when proofreading, copy-editing, or verifying English in any docs/**/*.mdx chapter or code comment in this repo. Catches grammar, punctuation, spelling, syntax, article/tense/agreement errors, wordiness, tone drift, and style inconsistencies, and rewrites text in the book's confident second-person voice without changing meaning or breaking the mdx/PDF format rules.

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

Build or refine UI color systems, warmth, semantic color, and color-based hierarchy in designs that are too gray, monochromatic, or missing color meaning. Use when the user mentions dull colors, gray UI, missing warmth, weak semantic color, or a need for stronger color hierarchy.

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

Add or refine depth through elevation systems, raised and inset surfaces, layered overlap, and meaningful shadow behavior so interfaces feel structured instead of flat. Use when the user mentions depth, elevation, shadows, layering, flat cards, pressed states, drag feedback, or inset controls.

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

File-level knowledge substrate via git notes. Read notes before working on files, leave notes after meaningful work. Daimonic spores carry creator identity across sessions.

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

Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.

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

Research the etymology of a word by tracing proto-language roots, identifying cognates across language families, documenting semantic drift with dated attestations, and flagging folk etymologies. Use when investigating word origins, comparing cognate sets across related languages, charting historical meaning changes, or debunking popular but unsupported origin stories.

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

Implement electronic signatures compliant with 21 CFR Part 11 Subpart C and EU Annex 11. Covers signature manifestation (signer, date/time, meaning), signature-to-record binding, biometric vs non-biometric controls, policy creation, and user certification requirements. Use when a computerized system requires legally binding electronic signatures for GxP records, when replacing wet-ink signatures in regulated workflows, when implementing batch release or document approval workflows, or when a regulatory gap reveals missing signature controls.

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

Statically enforce a privacy/redaction boundary on an artifact tree before publication, the way an AST checker enforces a code contract. Builds a two-tier gate — a shape-based deny-list (regex over identifier shapes) plus a structure-aware tier that parses JSON/HTML/SVG/Markdown/code and asserts sensitive content cannot appear in meaningful positions — with a strict exit-code contract, label-only output that never echoes the patterns themselves, and false-positive narrowing instead of suppressions. Use when gating a public mirror, a disclosure draft, a wire-capture export, or any artifact that must pass a leak check before it ships, and when a plain line-grep is too coarse to trust.

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