Skip to content
Agentmart
Submit a tool

dilaya-frontend

Use when giving a Dilaya app a website: enable it, write and deploy its handler, sign-in, static pages, staging, named actions.

Skill by hereya

IndexedMIT
Write a review

Chalk Labs

Need help deploying dilaya-frontend?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/hereya-dilaya-frontend

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when giving a Dilaya app a website: enable it, write and deploy its handler, sign-in, static pages, staging, named actions.

Use cases: frontend, devops, writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Nov 1, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/dilaya-frontend

What's inside

Skill name
dilaya-frontend
Description
Use when giving a Dilaya app a website: enable it, write and deploy its handler, sign-in, static pages, staging, named actions.
License
MIT
Instructions
29 lines in SKILL.md · view on GitHub

Files (16)

  • SKILL.md
  • actions.md · references/
  • architecture.md · references/
  • deploy.md · references/
  • enable.md · references/
  • flow.md · references/
  • handler.md · references/
  • isolation.md · references/
  • login.md · references/
  • mix.md · references/
  • package.md · references/
  • sources.md · references/
  • staging.md · references/
  • static.md · references/
  • templates.md · references/
  • versions.md · references/

SKILL.md (first lines)

Tool names below are the Dilaya connector's tools; your client may show them with a prefix (e.g. `mcp__dilaya__query`).

# Per-app web frontend

Give an app a **standalone web page** real people open in a browser — no Claude, no AI in the loop. It is served by a **per-app Lambda** that runs Node handler code you write and reaches ONLY its own app's SQLite database + files (isolated — see the end). **A site is PRIVATE by default**: the first `enable-frontend` provisions passwordless e-mail login and the platform closes the site, unless you give `public: true` — a showcase site, a landing page, a menu, anything meant for everyone, needs that explicitly (§5).

> **What a frontend is.** A real website other people visit on their own URL, with no AI in the loop — as opposed to answering in the conversation, which is what you do for the person you are chatting with.

## Sections

This is the table of contents, not the recipe: read the sections a step needs before acting on it.

- [App templates — check these FIRST (before writing any `handler.js` or HTML)](references/templates.md) — `templates`
- [Choosing the architecture — YOU decide, don't ask the user](references/architecture.md) — `architecture`
- [Dynamic pages, static sections — mix freely](references/mix.md) — `mix`
- [Flow (dynamic)](references/flow.md) — `flow`
- [1. Turn the frontend on](references/enable.md) — `enable`
- [2. Write the handler](references/handler.md) — `handler`
- [3. Package + upload](references/package.md) — `package`
- [4. Deploy + test](references/deploy.md) — `deploy`
- [5. Login — private by default, public on request (per-app auth)](references/login.md) — `login`
- [6. Static sections — pre-built pages served from the edge](references/static.md) — `static`
- [How sources travel between sessions — zip or git (the app remembers)](references/sources.md) — `sources`
- [Deployment versions & rollback](references/versions.md) — `versions`
- [Optional staging environment](references/staging.md) — `staging`
- [Actions — freeze an exact treatment in the backend, and CALL it](references/actions.md) — `actions`
- [Isolation](references/isolation.md) — `isolation`

From hereya/dilaya-plugin, MIT.

More from hereya/dilaya-plugin

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 5, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from hereya

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get dilaya-frontend running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying dilaya-frontend?

CallGet help
Cite this page

dilaya-frontend skill. Agent Mart. https://agentmart.dev/skills/hereya-dilaya-frontend (last updated 2026-10-24)