Build kit / Knowledge

An internal knowledge assistant

Answer team questions using approved information and role-based access.

Your app idea

Describe the
app you want.

Tell your agent what you want the app to do. You can work through the details together. This page does not save your changes.

The business or clientWhat the app should doSoftware you use & tools you build with

Use a summary of the business. Keep credentials and sensitive client records out of prompts.

The maintained Swirls agent instructions

Help me design and build: An internal knowledge assistant.

Intended outcome: An internal application backed by a Swirls agent that answers questions from approved sources and identifies uncertainty.
Business / client: [Describe the business or client]
Process and requirements: [Describe the process, people, rules, and exceptions]
Existing software and preferred frontend: [List existing software and preferred coding tools]

Use Swirls as the backend for workflows, agents, durable data, and integrations. Keep the frontend aligned with my chosen tools. Use the Swirls SDK for supported typed interfaces. Enforce business rules and authorization in the backend; do not rely on UI-only checks.

First read the maintained Swirls language skill at https://swirls.ai/.well-known/agent-skills/swirls-lang/SKILL.md and its referenced rules. Follow its complete-system design workflow before writing DSL. If you cannot access those instructions, stop and explain what is missing. Do not invent Swirls syntax, SDK methods, or platform capabilities.

Clarify these questions:
- Which sources are authoritative?
- Who can access each source?
- How should unanswered questions be handled?

Describe the complete system: interface, roles, access boundaries, data, workflows, agents, integrations, failure handling, and production responsibilities. Identify assumptions and missing capabilities. Present the plan for review before implementation. Treat the client details above as requirements to clarify, not permission to access external systems.

After approval, build in small verifiable steps. Validate .swirls files using the documented tooling. Keep credentials out of prompts and browser code. Assess hosting and networking against the actual runtime; do not assume private connectivity is already configured. Obtain explicit authorization before deploying or changing production resources.

Acceptance checks:
- Restricted information stays restricted.
- Answers identify their source and uncertainty.
- The team can maintain and refresh the knowledge sources.

Report what works, what was tested, and what still requires configuration or review.

Things to test

Check the
app works.

Restricted information stays restricted.
Answers identify their source and uncertainty.
The team can maintain and refresh the knowledge sources.

An internal knowledge assistant

Describe theapp you want.

Check theapp works.

Describe the
app you want.

Check the
app works.