app-builder

Build self-contained DenchClaw apps with a .dench.yaml manifest and entry HTML.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/putrawitama/DenchClaw --skill app-builder-putrawitama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-builder
Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/app-builder
Command: npx skills add https://github.com/putrawitama/DenchClaw --skill app-builder-putrawitama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DenchClaw app development often requires assembling isolated components and boilerplate to run self-contained apps within the workspace. This Skill provides a clear blueprint for creating self-contained apps that live inside DenchClaw's workspace, expose a standard manifest, and bridge to DenchClaw platform APIs for data, UI, and inter-app collaboration.

Core Features & Use Cases

  • Self-contained app architecture that runs inside the workspace with a .dench.yaml manifest and a clean entry point.
  • Bridge to platform APIs (dench.app, dench.ui, dench.db, dench.objects) to build interactive dashboards, tools, and widget-style components.
  • App lifecycle patterns, per-app storage, and inter-app messaging to compose multi-app experiences like dashboards composed of widget apps.

Quick Start

Create and wire up your first app by adding a folder apps/my-app.dench.app with a manifest and an entry HTML.

Frequently Asked Questions about app-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a self-contained app inside my workspace?

To build a self-contained workspace app, you create a folder containing a .dench.yaml manifest, an entry HTML page, and configure proper permissions to access bridge APIs. This architecture allows the app to run natively inside the DenchClaw workspace environment.

What is a .dench.yaml manifest used for in app development?

A .dench.yaml manifest is used to define the standard configuration and permissions for a self-contained workspace app. It exposes the app to the DenchClaw platform, enabling access to bridge APIs like dench.app, dench.ui, dench.db, and dench.objects.

How do I connect my dashboard to workspace data using DuckDB?

You connect your dashboard to workspace data by leveraging the dench.db bridge API within your self-contained app. This allows your interactive dashboards and widget-based components to query DuckDB and access workspace data directly.

Can I build widget-based components that communicate with each other?

Yes, you can build widget-based components that communicate using inter-app messaging patterns. This allows you to compose multi-app experiences, such as interactive dashboards made up of multiple individual widget apps sharing data.

Does building workspace apps require external dependencies?

No external dependencies are required to build DenchClaw workspace apps. The architecture relies entirely on creating a .dench.yaml manifest, an entry HTML page, and utilizing the platform's native bridge APIs for functionality and data access.