7,442 件 ・ 人気順
概要と使いどころ
Design an inquiry sequence anchored in a local ecosystem that embeds science or geography curriculum content. Use when teaching through local living systems like gardens, ponds, or hedgerows.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign a learning space using biophilic design principles to improve focus, calm, and wellbeing. Use when classroom environment contributes to restlessness, poor attention, or stress.
日本語の概要は準備中です。原文の説明を表示しています。
Design a scope and sequence showing vertical and horizontal curriculum coherence across a programme or year. Use when building new programmes, restructuring subjects, or ensuring progression.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a unit using backwards design from desired outcomes through assessment evidence to learning activities. Use when starting a new unit or redesigning an existing one from standards.
日本語の概要は準備中です。原文の説明を表示しています。
Design a sequence where students compare AI's handling of the same question across disciplines, developing a mental model of where AI is reliable vs. distorting based on knowledge type.
日本語の概要は準備中です。原文の説明を表示しています。
Design the transition from worked examples to independent problem-solving using expertise-reversal principles. Use when students follow examples but cannot solve problems alone.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign a direct instruction sequence to include productive struggle before the explanation phase. Use when teaching concepts that benefit from failure-first approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Script a multi-turn tutoring dialogue with branching responses for anticipated student difficulties. Use when designing AI tutors, chatbot interactions, or structured one-to-one support scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Design an adaptive assessment loop where each student response triggers the next instructional move. Use when building technology-enhanced formative assessment cycles.
日本語の概要は準備中です。原文の説明を表示しています。
Design deliberately flawed examples that develop error-detection skills and deepen understanding. Use when students make characteristic errors and need practice spotting mistakes.
日本語の概要は準備中です。原文の説明を表示しています。
Map knowledge components and skill hierarchies for a cognitive tutoring system or adaptive learning platform. Use when designing intelligent tutoring software or skill-based mastery systems.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and redesign AI-generated feedback for pedagogical quality, timing, and learning impact. Use when building or reviewing automated feedback in digital learning tools.
日本語の概要は準備中です。原文の説明を表示しています。
Design AI-supported collaborative tasks that structure group interaction and address participation problems. Use when students struggle to collaborate effectively on group tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a cascading hint sequence for a problem type, revealing progressively without giving answers. Use when designing tutoring dialogues or scaffolded worksheets.
日本語の概要は準備中です。原文の説明を表示しています。
Structure a direct experience into a full learning cycle with concrete experience, reflection, and conceptual transfer. Use when planning field trips, simulations, or practical tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Map the epistemic structure of a subject to determine knowledge types and inform curriculum sequencing. Use when designing courses, restructuring programmes, or analysing knowledge architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Design a project-based learning brief with a driving question, milestones, and assessment criteria. Use when planning PBL units, inquiry projects, or extended investigations.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.
日本語の概要は準備中です。原文の説明を表示しています。
Run an attorney-facing knockout/availability trademark search across the United States and Canada. Use whenever a user (founder, client, or attorney) asks whether a brand, mark, name, logo, slogan, or product name is "available," "free to use," "clearable," or "already taken" — or asks Claude to "search the trademark register," "check USPTO," "check CIPO," "do a knockout search," "clearance search," "availability search," or "see if [mark] is trademarked." Trigger even when the user phrases it casually ("can I call my company X?", "is this name taken?"). Covers federal USPTO (TESS/TSDR), federal Canada (CIPO), common-law/web/state, and WIPO Madrid international. Output is a knockout availability memo with green/yellow/red verdict for attorney review. Includes professional-responsibility gating (AI-use disclosure, conflict check, scope confirmation) before substantive analysis. Not legal advice — produces work product for attorney sign-off.
日本語の概要は準備中です。原文の説明を表示しています。
Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'reporting hierarchy', 'HQ vs regions', 'who is the decision maker', 'comms rhythm', 'meeting cadence', 'status call schedule'.
日本語の概要は準備中です。原文の説明を表示しています。
RFP creation, distribution, evaluation, and shortlisting for in-house legal teams selecting outside counsel. Draft a new legal services RFP from scratch, evaluate firm responses against weighted criteria, produce a shortlist recommendation with selection rationale for GC sign-off, or design the end-to-end RFP process from scratch. Trigger on: 'draft an RFP', 'run an RFP process', 'evaluate firm responses', 'score the RFP submissions', 'which firms should we shortlist', 'selection recommendation', 'how do we run a panel RFP', 'RFP for legal services', 'pitch process', 'firm selection process', 'compare the proposals', 'we're reviewing our panel', 'panel refresh RFP', 'we need to go to market', 'request for proposal', 'evaluate the pitches', 'which firm won the RFP', 'write a legal RFP', 'RFP evaluation criteria', 'design the RFP process', 'how do we weight the criteria'.
日本語の概要は準備中です。原文の説明を表示しています。
Panel structure design, firm selection criteria, right-sourcing analysis, and coverage gap assessment for in-house legal teams. Build panel frameworks from scratch or formalise existing informal arrangements. Define weighted selection criteria for firm evaluation. Run right-sourcing analysis (ABC tiering) to identify work sent to expensive providers that doesn't require that level of resource. Assess existing panels for practice area, geographic, and capability gaps. Trigger on: 'design our panel', 'how many firms do we need', 'panel structure', 'firm selection criteria', 'which firms should we use', 'right-sourcing', 'are we sending work to the right firms', 'panel gaps', 'too many firms', 'consolidate our panel', 'we need a firm for', 'preferred provider', 'panel tiers', 'do we need BigLaw for this', 'convergence', 'D&I panel targets', 'how do we choose firms'.
日本語の概要は準備中です。原文の説明を表示しています。
Audits a legal document against legal design principles. Scores the document on six pillars: language patterns (bureaucratese, archaisms, passive voice, nominalization), readability (Flesch Reading Ease and language-specific equivalents), structure and navigation, hidden conditions (material obligations buried away from their headings), statutory duplication (restating the law instead of citing it), and visual hierarchy where layout is available. Assessment-only; does not rewrite the document. Works on English, French, and German documents, inferring the applicable jurisdiction from the document's language and textual signals: governing-law clause, statute citations, party addresses. Use when a user shares a legal document (contract, NDA, T&C, privacy policy, internal policy) asking how good the drafting is from a legal design perspective, whether it is readable, whether it contains buried clauses or restates the law, or how it scores on Flesch / LIX / Amstad / Kandel-Moles readability metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Export Administration Regulations (EAR, 15 CFR Parts 730-774) compliance advisor — ECCN classification across all 10 CCL categories and 5 product groups (A-E), EAR99 determination, jurisdiction analysis (EAR vs ITAR order of review), license requirement analysis via Country Chart, all license exceptions (LVS, GBS, CIV, TMP, RPL, GOV, TSU, ENC, TSR, APP, BAG, AVS, ACE), end-user/end-use controls (Entity List, Denied Persons List, Unverified List, MEU List), deemed export rules, Foreign Direct Product Rule (FDPR), de minimis thresholds, 10 General Prohibitions, SNAP-R license applications, voluntary self-disclosure, civil/criminal penalties, Export Compliance Program (ECP) design, and EAR vs ITAR jurisdiction determination. Use for any dual-use export control, CCL classification, or BIS compliance question.
日本語の概要は準備中です。原文の説明を表示しています。