「vocabulary」の検索結果

Use only after explicit Codex `$superloopy:superloopy-backend` or Claude Code `/superloopy:superloopy-backend` invocation, a backend task beginning with leading `loopy` or `루피`, or an active Superloopy loop routes backend work here. Relevant work includes backend application boundaries, APIs, persistence, migrations, transactions, background jobs, caches, events, reliability, security, and runtime database-agent tools. Plain API, server, database, SQL, or agent vocabulary does not activate this workflow.

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

Use only after explicit Codex `$superloopy:superloopy-frontend` or Claude Code `/superloopy:superloopy-frontend` invocation for supported screen-based application UI across browser-hosted Web, interactive deployed content-led Web, desktop, mobile/tablet, embedded/hybrid, Qt, custom-rendered, or mixed targets, such a task started with a leading `loopy` or `루피`, or an active Superloopy loop explicitly routing it here. Do not activate from UI, frontend, desktop, mobile, or framework vocabulary alone, or for TV, wearable, XR, automotive, game UI, TUI, static media/document artifacts, or non-UI work.

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

Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.

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

Domain knowledge for SMB industry products — the vocabulary, the entities a spec must model, the incumbent to route around, and what a naive build gets wrong — one file per industry, plus local SEO and money-on-a-phone. Read the one file that applies before speccing or building the product.

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

Analyse text complexity across quantitative, qualitative, and reader-task dimensions with scaffolding recommendations. Use when selecting texts, assessing readability, or planning reading support.

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

Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.

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

MD3 vocabulary, component catalog, and a compliance-audit rubric across Web/Flutter/Compose. Use for MD3 tokens/components or an audit -- RIPDPI disables dynamic color (see android-compose-patterns).

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

Guide a researcher step by step into an unfamiliar research field, or decode a paper, abstract, figure caption, or referee comment they cannot parse. Builds understanding in rungs (motivation, vocabulary, core framework, methods, frontier), anchored to what the user already knows, with a checkpoint before each advance. Use when the user says they are new to a field, asks what a research area or method is, says an explanation was too technical, asks to be walked through something step by step, asks for a reading path, or supplies dense research text. Trigger even when the user only names an unfamiliar field or pastes an abstract without asking to be taught. Do not trigger for a one-line summary, a short overview request, or a direct factual answer; do not use it for translation, editing, search, debugging, or specialist questions inside the user's own field. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域.

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

Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of imposing a published one. Use when the user wants to record a decision, write an ADR, supersede an existing decision, audit or lint a decisions folder, check that an ADR index is in sync, or asks "why did we decide X". Deduces the filename scheme, section set and status vocabulary from the records already there; ships a validator with an exit code, so the audit is a check and not an opinion.

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

Remove the AI-script tells viewers hear in a TikTok spoken script and caption: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, performed sincerity, written-not-spoken phrasing, "hey guys" filler; caps em dashes. Includes --mode audit pre-film check (hook, completion design, caption fit) and --mode profile. Not for beating AI detectors (no edit reliably does). Not for writing from scratch (use tt-hook-scripter). Keywords: humanize script, de-AI, audit before filming.

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

Following what organisms do — behavior, metamorphosis, host-plant relationships, social dynamics, and the long-form ethograms that reveal how species actually live. Covers the vocabulary of ethology, the structure of a life cycle, the classic categories of species interaction, the discipline of recording behavior without premature interpretation, and the gap between a single observation and a statistically useful record. Use when the task is to understand or record what a species does rather than what it is.

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

Foundational concepts in nutrition science — macronutrients, micronutrients, energy balance, Atwater factors, reference intakes (DRI/RDA/AI/UL), food composition tables, and the methods of human nutrition research. Grounds the rest of the department in a shared vocabulary and in the measurement limits of the field, including controlled-trial history, observational-study limits, and the biochemical basis for calorie accounting. Use when a question asks what something "is" nutritionally, how energy and nutrients are measured, or what the reference numbers mean.

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

Identifying species in the field using dichotomous keys, gestalt recognition, diagnostic features, and habitat context. Covers the working identification protocol from first encounter through confidence-rated record, the vocabulary of field marks, the discipline of negative evidence, and the honest reporting of uncertain IDs. Use when the task is to name a living organism encountered in the field.

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

Comparative framing across contemplative and mind-body traditions — Sōtō Zen and Rinzai Zen, Theravada vipassana, Tibetan Vajrayana, classical yoga and its eight limbs, Daoist internal cultivation, secular MBSR and MBCT, engaged mindfulness as Thich Nhat Hanh teaches it, Christian contemplative prayer, Sufi dhikr, the Hesychast tradition of the Eastern Orthodox church — for the routing agent who has to understand where a user is already standing before recommending a practice. Covers the pedagogical voice of each tradition, the places they overlap, the places they genuinely disagree, and the non-sectarian framing the college department uses. Use when a user arrives with a prior tradition, when a query spans more than one tradition, or when the agent needs a vocabulary for what is shared and what is lineage-specific.

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

Reading a habitat — identifying biome, plant community, food web structure, successional stage, and the keystone species that hold the system together. Covers the elevational and latitudinal gradients that Humboldt first mapped, the structural vocabulary for describing a habitat, the core concepts of food-web and trophic analysis, and the practice of diagnosing habitat health from indicator species. Use when the task is to understand a place rather than a species.

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

Remove the AI tells readers react to in a Facebook Page post: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, announcement auto-pilot. Also --mode audit (under-80 sweet spot, hook, engagement bait), --mode profile (learns how you write) and --mode interview (fills your Story Bank: the stories, scars and numbers posts are made of). Not for writing from scratch (use fb-post-writer). Keywords: humanize, de-AI my post, interview me, audit before posting.

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

Write or rewrite prose so it sounds like a human wrote it — not a frontier model. Named in homage to Rabindranath Tagore, whose prose carried what frontier models reach for and miss: a point of view, specificity over abstraction, and restraint over puffery. Merges two complementary approaches: a 29-pattern catalog of AI tells (from humanizer) plus an 8-rule operating system with an 8-dimension scoring gate (extending stop-slop). Use when drafting, editing, or reviewing any prose: essays, posts, docs, reports, emails. Detects and removes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary, passive voice, negative parallelisms, filler phrases, inanimate-verb constructions, narrator-from-a-distance voice, and metronomic rhythm. Adds back the things AI writing usually lacks: point of view, stakes, specificity, restraint, varied rhythm, and trust in the reader.

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

Remove the AI tells readers react to in a Threads post: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, performed sincerity. Also --mode audit (500-char fit, hook, hashtag cap), --mode profile (learns how you write) and --mode interview (fills your Story Bank: the numbers, turning points and stories posts are made of). Not for writing from scratch (use threads-post-writer). Keywords: humanize, de-AI Threads post, interview me, audit before posting.

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

Visual vocabulary, design terminology, and prompt engineering strategy for Stitch. Reference this when you need layout pattern names, aesthetic style terms, color structure formulas, or device guidelines.

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

Use when ingesting text samples to extract quantitative writing style metrics. Produces a structured JSON style profile with vocabulary patterns, sentence structure, tone markers, and formatting preferences. Invoke before voice-clone-generator to establish style constraints.

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

Manage the project's layer vocabulary — list allowed layers with file counts, add new layers, or safely remove unused layers. Reads the shelf-index for usage data; writes CLAUDE.md atomically. No agent dispatch.

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

Use when project vocabulary is fuzzy, overloaded, disputed, or needed before naming docs, schemas, commands, skills, code, plans, or memory.

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

Eight tested identity approaches for Claude prompts, each shaping depth, vocabulary, reasoning style, and what Claude treats as obvious vs. requiring explanation. Use when the user wants a specific identity template — retrieving, reviewing, customizing, or building a role definition. Trigger on: "give me the Strategic Advisor identity," "show me the identity template for," "I need a Technical Architect role," "build a custom role for," "show me all available identities." Also use when reviewing a prompt's identity layer or when output lacks domain-appropriate depth. Provides 8 tested approaches across strategy, technical, research, communications, and operations domains plus a template for building custom identities. If the user is unsure which identity fits their task, use rootnode-block-selection first if available. Do NOT use for evaluating complete prompts — use rootnode-prompt-validation if available. Do NOT use for full prompt assembly — use rootnode-prompt-compilation if available.

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

把用户对 HarmonyOS、ArkUI、Canvas 或代码生成产品动效的模糊描述转换为准确术语、相近概念和可能的 ArkUI 能力，例如“松手像急刹车”“拖过头有阻力”“页面像从同一个卡片长出来”“后端没完成却显示成功”。用于命名、检索和编写提示词；不要用于完整设计审视、传统视频剪辑、镜头叙事、直接实现或构建问题。

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