Generates assisted setup wizard pages for Business Central setup tables following Guided Experience patterns. Creates NavigatePage with step-based navigation using visibility controls, banner images (WIP/Finished from Media Repository), temporary source table, footer actions (Back/Next/Finish with InFooterBar), OnOpenPage trigger (InitRecord, EnableControls, LoadSetupBanner), OnQueryClosePage trigger with unsaved changes confirmation, navigation procedures (NextStep with Step Option variable, EnableControls with Case statement, SetControlsStepXX boolean updates), commit procedure using TransferFields pattern, and registration codeunit with OnRegisterAssistedSetup event subscriber for Guided Experience. Integrates with Assisted Setup page and Extension Management. Supports multi-step workflows with welcome step, configuration step(s), and review/finish step. Uses InstructionalText for user guidance. Completes setup via GuidedExperience.CompleteAssistedSetup. Use when creating setup wizards, implementing assisted setup for extensions, adding guided configuration to modules, creating multi-step setup pages, registering with Guided Experience framework, or building NavigatePage wizards with step navigation.
Manages Franklin Baldo's Suno profile as a whole — bio, genre tags, pinned songs and their captions, and playlists — using the reverse-engineered Suno write API. Use when wording or applying a profile bio, choosing genre tags, writing pinned-song captions, creating or curating a playlist, or drafting the profile's overall curatorial identity. Every write to Suno requires Franklin's explicit per-action authorization; this skill documents what's possible and how to word it well, it does not grant standing permission to change anything.
Technology-agnostic guidance for modular systems: bounded contexts, clear boundaries, composability, state isolation, explicit contracts, failure containment, scaffolding workflows, split/merge criteria, sub-units inside a context, and compliance review signals. Use when designing or reviewing module structure, service boundaries, package layout, cross-cutting dependencies, "how should we split this?", modularity assessments, coupling between domains, greenfield context design, or architecture discussions without assuming a specific framework, language, or repository layout. Do NOT use for executing the full Patterns 1–5 repo decomposition pipeline or per-pattern inventories (use modular-decomposition), phased extraction roadmaps as the main deliverable (use decomposition-planning-roadmap), or end-to-end legacy migration strategy (use legacy-migration-planner).
Operate Argo CD without fighting the controller: establish which repository and generator own desired state, explain OutOfSync and drift, review rendered changes before sync, order dependencies, choose prune and self-heal policy, recover by changing Git, and verify convergence from commit to workload. Use this skill when someone asks why Argo CD keeps reverting a kubectl edit, whether to sync or prune, how to structure sync waves, how to recover or roll back a GitOps deployment, why an ApplicationSet child changed, or how multiple sources produced an unexpected manifest. Also use its ownership workflow for Flux drift, while verifying Flux-specific controls in the installed controller documentation. Not for designing canary cohorts and promotion metrics (`release-strategy`), authoring workload probes and resources (`k8s-workloads`), or diagnosing a live broken cluster (`k8s-triage`).
Extract a selected code block into a named function. Primary path uses the language server's extract-function code action; falls back to manual extraction when no code action is available. Validates captured variables, scope shadowing, and compilation after extraction.
Chapter-pipeline Step 3 for your book — check that every example, dialogue, citation, and illustration in the chapter does the work the surrounding prose says it does. Three tests: (a) does the example demonstrate the pattern the chapter labels it with; (b) is each foreign-language or technical term glossed at first use in the chapter; (c) is each source-jump bridged so the reader sees why the chapter moves from one authority to the next. Flag conflations, mismatches, missing glosses, and name-list stretches without bridges. Use when the user says "run the example-fit check," "do the examples fit," "check the illustrations in chapter X," "check glosses," "check the source jumps," or when running the chapter-pipeline skill (Step 3). Also invoke when the user reports that "this example doesn't fit," "this quote doesn't match the claim," or "these scholars read like a name-list."
Use a live Jupyter kernel for stateful, iterative Python execution via hamelnb. Load this skill when the task involves exploration, iteration, or inspecting intermediate results — data science, ML experimentation, API exploration, or building up complex code step-by-step. Uses terminal to run CLI commands against a live Jupyter kernel. No new tools required.
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
Audit a website against the Forter Agentic Readiness Guide. Loads the 25 weighted rubrics in `audit/`, probes the target site (and optional source code), scores each guideline Pass/Partial/Fail/N/A with sub-check granularity, and produces a prioritized fix report. Use when a user asks "score my site against the agentic readiness guide", "audit https://… for agent readiness", or "what do I need to fix to be agent-ready".
Use when a solution needs a coherent structure before implementation or production for Software testing and release assurance: unit testing for cross-platform behavior. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Technology-agnostic guidance for modular systems: bounded contexts, clear boundaries, composability, state isolation, explicit contracts, failure containment, scaffolding workflows, split/merge criteria, sub-units inside a context, and compliance review signals. Use when designing or reviewing module structure, service boundaries, package layout, cross-cutting dependencies, "how should we split this?", modularity assessments, coupling between domains, greenfield context design, or architecture discussions without assuming a specific framework, language, or repository layout. Do NOT use for executing the full Patterns 1–5 repo decomposition pipeline or per-pattern inventories (use modular-decomposition), phased extraction roadmaps as the main deliverable (use decomposition-planning-roadmap), or end-to-end legacy migration strategy (use legacy-migration-planner).
Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a specific model is deployable (`gcloud ai model-garden models list-deployment-config`), query deployment cost, troubleshoot deployment errors (like quota limits), or undeploy/clean up endpoints. Also use when copying and deploying a 1P Tuned Model. Don't use for pure listing/discovery questions of the form "is X deployed?", "list my endpoints", or "which regions have models running?" — for those use `agent-platform-endpoint-management`. Don't use for running model evaluations (use `agent-platform-eval-flywheel` skill).
Enforces functional-core purity rules: PURE-1 (no side effects in core/ modules — no I/O, no clock, no RNG, no logging), PURE-2 (no ambient/global state reads in core), PURE-3 (mock-required-to-test signal — if a function needs a mock to test, it isn't pure and belongs in shell). Loaded by the conductor for write and review operations when core-layer code is in scope. Layer detection follows the conductor's Section 14.