The tools behind the work

Version 0.3.0 package and workflow verified. Its remote Design connection is separately unverified.

Why it exists

A design brief should not require choosing a different specialist for every step.

How it helps

Coordinates branding, app visuals, illustration, motion, 3D and media through one complete workflow.

Example

Create an app icon and matching launch artwork from one approved brief.

BDL orchestration with attributed third-party specialist instructions and native engines.

Includes: beyond-design, beyond-design:use-whole-toolkit.

Link to this entry

Version 0.3.0 package and workflow verified; service and account access are checked per project.

Why it exists

Website research, content, design and testing often become disconnected tasks.

How it helps

Selects the required specialists and carries a website brief through implementation and browser verification.

Example

Build a product page and check its mobile layout, navigation, content and forms.

BDL workflow integrating attributed design, search and web-development components.

Includes: beyond-webdesign, beyond-webdesign:use-whole-toolkit.

Link to this entry

Version 0.3.0 package and workflow verified. An audit does not itself change a site or account.

Why it exists

Generic SEO advice can ignore the actual business, location and search evidence.

How it helps

Combines current research, matched authorized analytics and read-only checks into a verified findings report.

Example

Investigate a service page using the correct company search and analytics properties.

BDL audit workflow with attributed upstream SEO, accessibility and performance specialists.

Includes: beyond-seo-audit, beyond-seo:use-whole-toolkit, Business dossier specialist, Live analytics specialist, AI search specialist, Existing-site audit specialist, Independent audit-report review.

Link to this entry

Version 1.0.68 package verified. Its Books MCP connection was also checked separately.

Why it exists

Agent-assisted financial work needs the correct company records and a reviewable draft.

How it helps

Connects authorized record reads and preparation of clients, draft estimates and draft invoices.

Example

Prepare an estimate draft for review in Beyond Books.

Includes: beyond-books skill, Codex package, Claude Code package.

Link to this entry

Version 1.0.20 package verified. Account connection and publication acceptance are separate checks.

Why it exists

Multi-brand publishing can lose the right company identity, approval or job status.

How it helps

Connects company-scoped drafts, Brand Truth checks, approvals, schedules and durable publishing status.

Example

Prepare a company campaign draft and inspect its approval before publication.

Includes: beyond-publisher skill, Codex package, Claude Code package.

Link to this entry

Version 2.1.0 source verified; designed for the supported OpenCode host rather than every agent app.

Why it exists

Long development conversations lose exact decisions and measured results during summarization.

How it helps

Uses native OpenCode hooks, bounded durable history and validated summaries while preserving the chosen model.

Example

Continue a long coding session with its latest result and owner corrections intact.

BDL integration for the independently developed OpenCode host.

Link to this entry

Why it exists

A local build can pass while the deployed workflow remains broken.

How it helps

Finds the real cloud target and records full-suite results against the deployed revision.

Example

Verify an account workflow against its actual deployed backend.

Link to this entry

Why it exists

Video, captioning and avatar references are spread across different tools.

How it helps

Routes an approved task to the relevant installed native workflow and its original usage guide.

Example

Choose an appropriate captioning workflow for a marketing clip.

BDL selection and integration; supporting avatar and video engines remain independently owned.

Includes: bdl-avatar-toolkit.

Link to this entry

Why it exists

Agents rebuild utilities that already exist or use the wrong project copy.

How it helps

Finds installed capabilities and reads their native instructions before choosing an implementation.

Example

Locate an existing browser-debugging tool before building another harness.

Includes: bdl-workstation-tools, beyond-workflow-index.

Link to this entry

Development preview only. Voice acceptance has not passed and real business phone routing is not activated.

Why it exists

Missed business calls lose useful intake and require repeated questions.

How it helps

Defines grounded caller intake, persistent notes and owner notifications for the developing answering service.

Example

Capture a caller request and read back its details before owner follow-up.

Includes: beyond-answering-assistant.

Link to this entry

Why it exists

App logos drift from the approved brand or ship without the right platform exports.

How it helps

Preserves the approved master, develops the app glyph and checks the complete native export kit.

Example

Prepare coordinated Android and Windows icons for a new Beyond app.

Link to this entry

Why it exists

Business workflows can duplicate records, lose money precision or cross company boundaries.

How it helps

Preserves product ownership, exact money and company isolation across business modules.

Example

Carry the correct CRM customer into a draft Books estimate.

Link to this entry

Workflow and native generation adapter source verified; this does not establish every model or a downloadable release.

Why it exists

Media generation can hide model substitutions, uploads and failed execution.

How it helps

Routes requests to the selected compatible native media engine through its shared workflow and adapter.

Example

Generate a product image with the explicitly selected compatible model.

BDL workflow and integration; generation engines and model weights retain their original ownership.

Includes: beyond-gen, Design generation MCP adapter.

Link to this entry

Why it exists

Ad hoc agent connections create inconsistent access and lifecycle behavior.

How it helps

Defines product-specific authenticated interfaces and native connection contracts.

Example

Connect an authorized agent to the correct business application interface.

Includes: beyond-mcp.

Link to this entry

Why it exists

A feature can look finished while its saved data and related views disagree.

How it helps

Coordinates application data, services and interfaces around a complete user outcome.

Example

Save a record and prove it appears consistently in the related application views.

Link to this entry

Why it exists

Screenshots and isolated tests can conceal broken real workflows.

How it helps

Checks user actions, downstream state, persistence, restart and recovery.

Example

Create a profile, restart the app and confirm its data and access rules remain correct.

Link to this entry

Why it exists

Website changes can ship without coherent search, accessibility or performance checks.

How it helps

Supplies the acceptance specialist within the complete Beyond WebDesign workflow.

Example

Check a landing page for crawlability, structured data and real browser behavior.

Includes: beyond-seo.

Link to this entry

Why it exists

Repeated generic compositions make different products look indistinguishable.

How it helps

Combines reference analysis, composition variety and rendered-quality checks.

Example

Develop a distinctive product showcase while preserving its brand identity.

Link to this entry

Why it exists

Shallow passing tests miss access restrictions and broken recovery.

How it helps

Uses meaningful failure cases, controlled fixes and actual-runtime verification.

Example

Confirm an unapproved account cannot access a protected asset.

Link to this entry

Why it exists

Recurring work can silently stop when a computer goes offline.

How it helps

Coordinates persistent jobs, retries and finite executors through Cloudflare Workflows.

Example

Resume a catalogue refresh after a temporary connection outage.

BDL automation architecture using the independently operated Cloudflare platform.

Includes: cloudflare-automation-hub.

Link to this entry

Why it exists

A decorative QR design can fail to scan or point to the wrong destination.

How it helps

Combines concept approval, destination proof, decode validation and a defined fulfillment process.

Example

Prepare a branded business QR sign and verify its final destination.

Includes: custom-qr-codes.

Visit Custom QR Workflow→

Link to this entry

Why it exists

Path escaping and text encoding can corrupt generated configuration files.

How it helps

Uses native parsing and literal file-writing techniques with saved-content checks.

Example

Write a Windows configuration while preserving every intended path and character.

Link to this entry

Why it exists

Inconsistent client folders make governing records and assets difficult to find.

How it helps

Prepares the approved workspace structure while preserving existing client material.

Example

Organize a new authorized website project before development begins.

Includes: new-client-directory.

Link to this entry

Why it exists

Generic search copy invents business facts and targets unsupported markets.

How it helps

Uses verified company facts, current guidance and matched search evidence.

Example

Rewrite a service page around actual customer demand and the real service area.

Link to this entry

Why it exists

Implementation can drift from an approved layout and visitor journey.

How it helps

Builds the selected site design within WebDesign and proves its browser behavior.

Example

Implement a responsive product page with working navigation.

Includes: web-design.

Link to this entry

Why it exists

Interactive graphics require coordinated scene, motion and performance decisions.

How it helps

Selects appropriate Three.js and WebGL techniques within the owning design workflow.

Example

Add a responsive interactive 3D product scene to an approved website.

BDL specialist workflow using independently developed graphics libraries.

Link to this entry

Four tool schemas responded in the authenticated connection check. Task execution remains with the native host.

Why it exists

Loading every available instruction wastes context and makes relevant tools harder to find.

How it helps

Provides bounded search, inspection and guide reading through a compact native MCP interface.

Example

Load one relevant tool guide for the current task.

Includes: Agent Library MCP, agent-library toolkit.

Link to this entry

Native measurement source and prior proof verified. The experimental audio assessor did not qualify as a quality or lip-sync judge.

Why it exists

Media comparisons often substitute unsupported quality claims for measurements.

How it helps

Measures decode results, loudness, hashes and frame geometry using native inspection tools.

Example

Check a generated clip for decode failures and measure its audio peaks.

Link to this entry

Current native hook source verified. Activation is optional; legacy Stop-Guard is not the current installed implementation.

Why it exists

An agent may stop before an implementation request has been completed.

How it helps

Adds optional per-conversation continuation hooks for supported agent hosts.

Example

Keep a long authorized development request under its chosen continuation rules.

Includes: beyond-stop-guard, Codex-Hooks, guard-start, guard-stop.

Link to this entry

Uses extractive verified indexing. Optional trained-model refinement remains disabled.

Why it exists

Directory maps become stale and do not explain the projects they contain.

How it helps

Observes permitted documents in finite runs and publishes source-identified project knowledge.

Example

Refresh project briefs after their governing records change.

Includes: bootstrap-agent.

Link to this entry

Why it exists

Separate agent-host copies drift or recreate intentionally removed workflows.

How it helps

Registers canonical skills through a finite manual operation with preservation and exact-content checks.

Example

Make one approved shared workflow discoverable in another supported host.

Includes: homebase-access.

Link to this entry

Why it exists

Interrupted or unpinned model downloads are difficult to reproduce and verify.

How it helps

Uses exact revisions, declared sizes and hashes while retaining resumable downloads and conflicting files.

Example

Download an explicitly selected model revision and verify its artifact.

BDL manifest and verification wrapper around the upstream Hugging Face CLI.

Includes: hf-model-download.

Link to this entry

Why it exists

Windows agent hosts need predictable MCP startup and shutdown.

How it helps

Uses shared native launch definitions and managed child-process lifecycles.

Example

Open an authorized tool connection and cleanly close its owned processes afterward.

Includes: mcp-launcher.

Link to this entry

Why it exists

The supported Pi host version does not include built-in MCP access.

How it helps

Registers native MCP tool schemas and forwards progress, cancellation and visible failures.

Example

Use an authorized business tool from a supported Pi session.

BDL host adapter using the official MCP SDK; Pi remains independently developed.

Link to this entry

Why it exists

A website walkthrough can accidentally send a real inquiry or payment request.

How it helps

Serves a local preview with rewritten navigation and refuses write requests.

Example

Review a responsive website without sending a real customer inquiry.

Includes: site-preview.

Link to this entry

Why it exists

Incorrect assumptions about the development environment cause repeated command failures.

How it helps

Combines measured Windows command rules with a generated environment and ownership map.

Example

Prepare a usable environment brief before starting a native build.

Includes: workstation-blueprint skill, workstation-blueprint toolkit.

Link to this entry

The authenticated master status responded during this audit. Imported references are not BDL-authored products.

Why it exists

A large tool collection is difficult to discover and connect consistently.

How it helps

Provides paginated capability discovery, native guides and routed access to configured interfaces.

Example

Find the correct invoice-draft capability and retrieve only its relevant guide.

Includes: beyond-master-toolkit skill, Master Toolkit MCP.

Link to this entry

Eighteen tool schemas responded. No financial operation was executed in this inventory check.

Why it exists

Financial tools need consistent company scope across agent clients.

How it helps

Exposes the native Books contract for authorized records and draft preparation.

Example

Prepare an estimate draft for the correct company.

Link to this entry

Twenty-seven tool schemas responded. Business-operation acceptance remains separate.

Why it exists

Agents need the same scoped client and lead records as the business application.

How it helps

Exposes native CRM operations through an authenticated interface.

Example

Inspect the authorized company lead pipeline.

Link to this entry

The current connection check failed. Source is present; earlier connection success is not a current all-clear.

Why it exists

Design production tools need consistent discovery and native usage contracts.

How it helps

Connects the design catalogue, guides and production adapters through one interface.

Example

Inspect a rendering adapter before choosing its production workflow.

BDL integration over separately owned production engines.

Includes: beyond-design-mcp skill.

Link to this entry

Three tool schemas responded. Individual model loading and inference were not tested here.

Why it exists

A client needs to know whether its selected local model can actually run.

How it helps

Exposes model discovery, readiness and generation contracts to authorized clients.

Example

Inspect the chosen model readiness before requesting inference.

BDL interface; model weights and inference engines retain their original ownership.

Link to this entry

Eight tool schemas responded. The standalone Content Creator app remains coming soon.

Why it exists

Content preparation needs access to its actual assets, drafts and job state.

How it helps

Exposes native content tools to supported authorized clients.

Example

Inspect prepared campaign assets before an explicitly authorized publishing step.

Link to this entry

Product configuration and plugin source verified; this inventory did not execute publishing or certify customer onboarding.

Why it exists

Publishing clients need company-specific drafts, approval and persistent job status.

How it helps

Provides the native Publisher interface to supported agent connections.

Example

Inspect a campaign draft and its approval before scheduling it.

Link to this entry

Native configuration source verified. No separate public connection or rendering acceptance is claimed.

Why it exists

Motion automation needs the actual project and compatible production engine.

How it helps

Defines a product-owned native connection and a Design production adapter.

Example

Inspect a selected motion project before a production job.

Link to this entry

Thirty tool schemas responded; browser actions were not executed in this inventory check.

Why it exists

Authorized agents need a consistent browser-diagnostics connection.

How it helps

Hosts and routes the upstream Chrome DevTools MCP through the BDL integration.

Example

Inspect an application performance trace during debugging.

BDL gateway integration. Chrome and its DevTools MCP are upstream products.

Link to this entry

Forty-nine tool schemas responded; no repository change was made by this inventory check.

Why it exists

Authorized repository workflows need a consistent agent connection.

How it helps

Hosts and routes the official GitHub MCP through the BDL integration.

Example

Inspect a repository issue alongside its relevant source.

BDL gateway integration. GitHub and its official MCP remain upstream products.

Link to this entry

One tool schema responded; this is not a new BDL reasoning model.

Why it exists

Agent hosts need a consistent interface to a structured reasoning helper.

How it helps

Hosts and routes the upstream reference server for configured clients.

Example

Organize a bounded debugging investigation into explicit steps.

BDL gateway around an upstream MCP reference implementation.

Link to this entry

Seven tool schemas responded; individual browser journeys were not tested here.

Why it exists

Agent hosts need a predictable browser-inspection interface.

How it helps

Hosts and routes a Puppeteer-based browser integration.

Example

Inspect a public page and capture its rendered state.

BDL gateway integration using independently developed browser tools.

Link to this entry

Why it exists

Search, crawling and advertising resources are scattered across unrelated repositories.

How it helps

Curates native references and usage routes while retaining each tool account and runtime requirements.

Example

Select an appropriate existing crawler for an approved website audit.

BDL curation of upstream tools; their source presence does not establish service access.

Includes: ads-seo-agent-toolkit.

Link to this entry

Why it exists

Motion and 3D projects span several different engines.

How it helps

Collects native animation, Blender, WebGL and scene-building references.

Example

Find a compatible reference workflow for a character-animation brief.

BDL curation; the referenced engines and instruction sources retain upstream ownership.

Includes: animation-agent-toolkit.

Link to this entry

Why it exists

UI components, testing and observability references are fragmented.

How it helps

Collects upstream interface, browser-testing and desktop-framework resources.

Example

Find a native test workflow for a responsive application.

BDL curation; individual frameworks and components remain independently owned.

Includes: gui-ui-ux-design-debug-toolkit.

Link to this entry

Why it exists

Agent research and implementation approaches are difficult to compare.

How it helps

Collects upstream orchestration, memory, retrieval and evaluation material.

Example

Compare existing evaluation methods before designing an agent benchmark.

BDL curation of research and tools, rather than a new BDL reasoning model.

Includes: reasoning-intelligence-agent-toolkit.

Link to this entry

Why it exists

Simulation work spans incompatible robotics and game environments.

How it helps

Maps references for established simulators so a project can choose its appropriate native environment.

Example

Identify a suitable simulator for an authorized robotics prototype.

BDL curation of upstream AirSim, CARLA, Gymnasium, MuJoCo, Godot and Webots references.

Includes: virtual-simulation-toolkit.

Link to this entry