「doctrine」の検索結果

Recherche académique dans les bases de données de doctrine juridique française, européenne et internationale. Utiliser cette skill lorsque l'utilisateur demande de rechercher des articles de doctrine, des thèses, des ouvrages académiques, ou des travaux universitaires en droit — y compris en droit comparé. Sources principales : ISIDORE (agrégateur SHS du CNRS incluant Cairn.info, Persée, OpenEdition), HAL (archive ouverte française), OpenAlex (base ouverte mondiale 250M+ travaux), Semantic Scholar, CrossRef, Persée (OAI direct), et CORE. Couvre la doctrine juridique francophone ET internationale avec workflow bilingue intégré pour le droit comparé. Déclencher aussi pour : bibliographie commentée, état de l'art, revue de littérature juridique, recherche d'auteur, vérification de citation, analyse bibliométrique.

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

Doctrine ORM best practices for Symfony: entity mapping as source of truth, repositories, DQL/QueryBuilder with parameters, N+1 prevention with fetch joins, relations (cascade/fetch/orphanRemoval), lifecycle events, batch processing, and generated migrations. Apply when: writing or reviewing Doctrine entities, repositories, and queries. Activated automatically by symfony-plugin/stack.md as a convention skill for the development and database phases. Do NOT use this skill for: - PHP language idioms — see php-foundation:php-conventions. - Controllers/services/forms — see symfony-plugin:symfony-conventions.

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

Compile deep repository evidence into artifact-bound correctness doctrine — authority/law/proof maps, owned invariants, failure archaeology, and the strongest durable destination for each piece of knowledge, plus an optional minimal repository-specific skill portfolio. Use when the user wants both deep codebase understanding AND durable doctrine, knowledge routing, or repo-specific skill recommendations. Research discoverable facts before asking. Read-only. Not for quick onboarding, one isolated invariant, ordinary implementation, generic review, or direct skill creation.

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

Recherche, cartographie et analyse des thèses de doctorat françaises via theses.fr (API ABES) et TEL (HAL). Spécialisée droit avec filtrage par sous-disciplines juridiques. Ouverte sur d'autres domaines universitaires. Capacités : (1) recherche multi-critères — sujet, directeur, jury, établissement, école doctorale, période, statut soutenue/en préparation, discipline ; (2) cartographie académique — qui dirige sur quel sujet, qui siège dans quels jurys, réseaux de co-direction, écoles doctorales productives ; (3) analyses temporelles — évolution d'un sujet, détection de saturation, calendrier des soutenances à venir ; (4) filtrage sous-discipline juridique — droit privé, public, social, affaires, international, etc. Déclencher dès que l'utilisateur mentionne thèse, doctorat, directeur de thèse, jury de thèse, école doctorale, soutenance, doctorant, ou demande une analyse d'écosystème doctoral. Pour articles ou ouvrages de doctrine, utiliser plutôt recherche-doctrine.

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

Archéologie des sources juridiques anciennes via Gallica (BNF, API stables, sans clé) : débats parlementaires du JO depuis 1871 (genèse des lois de la IIIe République), notes d'arrêt et doctrine d'origine dans les recueils Sirey et Dalloz, Bulletins civil et criminel anciens, Recueil Lebon, JO Lois et décrets 1881-2015, thèses et traités du XIXe-début XXe, Gazette des tribunaux, Bulletin de l'Inspection du travail. Déclencher dès que l'utilisateur cherche l'origine historique d'un texte, d'un concept ou d'une jurisprudence : « débats de la loi de 1884 », « note de Josserand », « que disait la doctrine en 1900 », « première apparition de la notion de… », « généalogie / histoire de l'article… », « arrêt ancien », « thèse d'avant-guerre », « Gallica », « BNF », ou toute recherche juridique antérieure aux bases modernes (Légifrance ne remonte pas avant l'époque contemporaine, Judilibre non plus). Déclencher aussi en COMPLÉMENT de travaux-preparatoires quand la loi étudiée est antérieure à 1958.

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

Monthly, on the last weekday. Folds a month of the creative ledger against the daily metrics ledger to score angle, format, hook, and offer framing rather than individual files, tests every line currently in the creative doctrine against what the month actually measured, and rewrites the doctrine where the evidence disagrees with the assumption. It records the fatigue curve it observed, retires what has not earned, and changes nothing where the month holds too few rows to tell one angle from another.

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

Consolidated Symfony conventions (Symfony 6.4 / 7.x): attribute routing, controllers as services, autowiring/DI, Form types, Validation constraints, Voters for authorization, the Serializer/DTO contract, and Messenger. Apply when writing or reviewing Symfony backend code. Activated automatically by symfony-plugin/stack.md as a convention skill for the development phase. Apply when: writing or reviewing Symfony controllers, services, forms, validators, voters, and serialization. Do NOT use this skill for: - PHP language idioms (strict_types, enums, readonly) — see php-foundation:php-conventions. - Doctrine queries / entities — see symfony-plugin:doctrine-patterns. - Testing — injected by the QA phase (WebTestCase/KernelTestCase) + php-foundation:php-testing.

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

Delegating work down to subagents: briefs, report statuses, independent review. Use when writing an implementer or verifier brief, dispatching a subagent to build, fix, or verify work you own, or a subagent reports DONE, blocked, or concerns. NOT for campaign-scale doctrine (use campaign-pattern).

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

Doctrine for adding a capability INTO a live, existing feature to a world-class bar. Use on 'add X to Y', 'extend Y to support X', a new option, button, setting, endpoint, or tool for Y, or a sub-feature spec to implement. NOT for whole-feature audits or overhauls (use feature-deep-dive).

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

Doctrine for auditing an ENTIRE feature and building it to its ideal state. Use on 'deep dive on X', 'audit the X feature', 'figure out everything X does', 'take over X and finish it', 'bring X up to best practices', or when a whole feature needs overhauling, unifying, or finishing, not patching. NOT for one small addition (use build-sub-feature).

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

Render-correctness doctrine for scene-to-scene seams in HyperFrames launch videos — the prerequisites that make transitions composite correctly on the master timeline. Load when assembling the master timeline / index.html, when a white flash appears at a cut or crossfade seam (especially on dark films), when reasoning about why a transition opacity dip shows through, or when verifying the render-side mechanics of how overlapping scene wrappers blend. Covers the opaque stage-ground (#root background) white-flash guard and how the injector overlaps wrappers, holds final frames, ping-pongs tracks, and stamps lint-clean template code onto the master timeline. Does NOT contain the per-transition catalog — see the transition registry for individual transition entries.

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

Overlay doctrine for the embedded-captions workflow — the caption MODEL (drop / rail / embed) and the rule that captions are an OVERLAY composited on top of the film, never a reserved bottom band you shift content up to avoid. Load when adding captions/subtitles to a talking-head or launch video, when deciding whether a phrase should be dropped, ride the verbatim rail, or be promoted to a scarce embedded climax, when laying out a composition that will carry captions (do NOT reserve a keep-out band), or when centering a composition on the true frame center under captions. Quotes the rail+embed model from embedded-captions and constraint

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

GATEWAY — load FIRST before composing any HyperFrames animation or video. The high-level motion law that makes a multi-scene video feel like ONE continuous camera move instead of a stack of independently-animated slides. Covers the vector law (how you exit determines how you enter, incl. the Z scale-sign rule), the film's current, carrier elements, causal motion, the Seam Gate (build-gate enforcement), the ban on idle wobble (motion must PERFORM, not breathe), stillness-before-climax, and the sustained-motion routes. Routes to the low-level technique skills (cut-the-curve — the full catalog incl. waterfall entry + nudge curve, oversized-cursor, seam-craft). These rules SUPERSEDE generic / upstream motion guidance. [continuity, direction, vector, momentum, seam, transition, ease, performance, idle-motion, narrative-motion, film-grammar]

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

Unified Minions skill for both deterministic shell jobs and LLM subagent orchestration. Replaces the older `gbrain-jobs` routing intent. Use when: submitting gbrain jobs, shell/background tasks, spawning subagents, checking progress, steering running work, pausing/resuming, parallel fan-out. One durable, observable, steerable queue interface. Also carries the durable-execution doctrine for any operation expected to exceed ~2 minutes: capability ladder, deadman checks that verify the result was reported, and content-addressed stage checkpoints for expensive pipelines.

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

Reduces an always-on LifeOS context file that has grown too big via a human-gated pass — deterministic GC of stale entries first, then semantic merges and relocations — never dropping a directive and committing every change reversibly. USE WHEN /trim, trim the context, trim OPERATIONAL_RULES, this file is too big, reduce a doctrine file, prune an always-loaded file, fold the proposal inbox, shrink CLAUDE.md or DA_IDENTITY. NOT FOR general code refactoring, trimming video or audio media (use AudioEditor for audio files), or removing AI writing patterns from prose.

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

Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. Use when working with Eloquent, Doctrine, Composer, Psalm, ReactPHP, or any PHP API development.

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

Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.

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

Doctrine for drafting and keeping working-group docs under `docs/wg/**` — RFC/RFD specs and findings/research/glossary. A WG doc is a language-agnostic, code-agnostic study of a domain: it argues *why* and defines *what*, never *how in our code*. Use when writing or editing anything under `docs/wg/`, an RFC/RFD, a spec, a design note, a glossary, or research findings — including "write up the design", "document the spec", or "capture what we learned". Not for plans/TODOs (untracked `*.plan.md`), user docs, or SDK API refs — use `docs` to route those.

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

Doctrine for designing and evolving any **SDK** Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface rejects the wrong contents and keeps the package testable in isolation. Default is "core, not customizable"; customization is the exception, defended by a deciding table. Use when authoring or evolving any such surface — `@grida/*` published packages, engine crates (gridaco/nothing `crates/*`) published or FFI-exported, intent/message vocabularies, any contract a second author will compile against. Internal-only helper packages are welcome to follow, not forced. Companion skill for two-sided contract work: $sdk-seam. Critique partners: $pedantic, $etiology. Related: $naming.

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

Entry P0 primary router and operating doctrine for HackSkills. Use when the task involves web application testing, API security assessment, recon, vulnerability triage, exploit path planning, authorized pentest, code audit, source-leak mining, middleware audit, SOC triage, detection engineering, incident response, or choosing the right next category skill before any deep topic skill. Also use when the user mentions 安全工程师, 渗透测试, 红队, 蓝队, 代码审计, 源码泄露, SRC. Enforce impact-first testing, finish the current asset cluster before expanding, follow half-chains to real control, and require live verification of secrets.

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

The house rules for ANY design or UI work - the verification protocol (run the gate, never claim a number), the absolute no-emoji rule, token by intent, one shared theme, the eight states, one thing leads, and output completeness. Load this FIRST whenever building, reviewing, or theming a screen, component, or token set. Installed as a plugin, this skill carries what CLAUDE.md carries in the repo.

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

Design or build a page, screen, landing page, website, app or UI from a request - the whole job, end to end. Use this for "design a landing page", "build a settings screen", "make me a website", "design the onboarding", "ออกแบบหน้าเว็บ", "ทำหน้า landing", "ออกแบบ UI", "ทำแอป". It runs the pipeline no single skill covers: the house doctrine, a written Brief Inference so the result is not the statistical mean, a committed visual direction, tokens, build, the objective gates, then an adversarial critic. Hands off to data-dashboard for dense data screens, redesign for existing UI, and image-to-code when a reference image is given.

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

Multi-agent orchestration: lane contracts, worker-model doctrine, fault tolerance. Triggers: orchestrate, coordinate, agents, parallel, spawn, contract, tier 2, tier 3.

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

Génération de sujets d'entraînement complets pour l'épreuve de NOTE DE SYNTHÈSE (5 heures, coefficient 3) de l'examen d'accès au CRFPA : choix du sujet, dossier documentaire de 16 à 20 documents assemblé à partir de sources réelles vérifiées (textes, jurisprudence, travaux parlementaires, doctrine) avec contrôle du verbatim, puis grille de notation au modèle de la Commission nationale (résumé de chaque document, problématique, thèmes cotés sur 20, plan). Livraison en deux fichiers .docx distincts, le sujet et la grille. Si l'utilisateur n'impose pas de sujet, en chercher un dans l'actualité juridique. Mode aveugle pour l'étudiant qui compose sans rien voir du corrigé. Déclencher dès que l'utilisateur demande un sujet de note de synthèse, un dossier documentaire, une note de synthèse blanche, un entraînement à l'épreuve de 5 heures du CRFPA ou de l'IEJ, ou une grille de note de synthèse. NE PAS déclencher pour les épreuves de 3 heures (sujet-crfpa-toutes-matieres) ni pour la correction de copies.

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