Results for “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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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).

The English summary is being prepared. Showing the original description.

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).

The English summary is being prepared. Showing the original description.

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).

The English summary is being prepared. Showing the original description.

Fix white flashes and blending problems between scenes in HyperFrames videos. This skill explains background setup, overlapping scene containers, final-frame holds, and timeline templates so transitions render with the intended appearance.

• Fixing white flashes between dark scenes
• Checking opacity dips during crossfades
• Assembling the master timeline

Plan HyperFrames videos so motion flows continuously between scenes. Match movement direction and speed across cuts, connect actions through visible causes, and verify scene boundaries while keeping each scene active through meaningful reveals or interactions.

• Plan consistent movement across scene transitions
• Connect scenes with a shared visual element
• Replace idle motion with reveals or interactions

Plan subtitles as layers over a video, deciding which spoken phrases to omit, show normally, or emphasize behind the subject. The guidance preserves full-frame composition and limits large embedded words to occasional key moments.

• Planning subtitles for a talking-head video
• Choosing words to emphasize behind the subject
• Centering a scene that carries subtitles

Design scene transitions and animated text using matched movement direction and speed across cuts. The catalog provides concrete settings for zooms, blur, word-by-word transitions, staggered entrances, and repositioning groups of elements.

• Connect scenes with matching motion
• Transition between headlines word by word
• Bring title elements in with staggered timing

Manage shell commands and AI agent tasks through a shared gbrain job queue. Track progress, steer agents, pause or resume work, and coordinate parallel tasks, with guidance for long operations, completion reporting, and reusable stage checkpoints.

• Run scripts as monitored background jobs
• Coordinate parallel research by AI agents
• Redirect, pause, or resume an agent task

Reduce oversized LifeOS instruction files while preserving distinct rules. Remove obsolete entries first, then propose approved merges, shorter wording, or relocation to reference files, with size measurements and reversible commits documenting the changes.

• Reducing an oversized CLAUDE.md
• Consolidating overlapping operational rules
• Cleaning up accumulated proposal entries

Build PHP 8.3+ applications with Laravel or Symfony, including typed models, services, APIs, and tests. Use static analysis, which checks code without running it, alongside automated tests to verify the implementation.

• Building APIs with Laravel or Symfony
• Separating business logic from controllers
• Creating typed data objects and domain models

Analyze past law course exams for recurring topics, question formats, and hidden issues. Compare those patterns with the current syllabus to suggest study priorities and review time, while clearly marking uncertainty about the upcoming exam.

• Comparing topic coverage across past exams
• Identifying recurring question styles and traps
• Allocating study time using the current syllabus

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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 English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.