One app, built by an agent, running on Fulcra

The stack

• Skillfulcradynamics/agent-skills, build-and-deploy-a-web-app
• TemplateSvelteKit (Svelte 5), Tailwind and DaisyUI, with sign-in and an API client included
• Sign-inFulcra accounts through Auth0's device flow; the session lives in an HTTP-only cookie
• DataFiles in Fulcra accounts, read and shared through the Fulcra API. No separate database.
• HostingA Fulcra deploy project: <name>.my.fulcra.ai, no hosting account needed
• ProcessThe skill's harness plans each milestone, builds it, and has a separate evaluator check it on the live site

Where the data lives

Every person signs in with their own Fulcra account. The team account owns the board. Everyone else reads what's shared with them, and admins write only to their own account.

Four patterns worth copying

1. Read a file someone shared with you

Pass the owner's Fulcra user ID on the request. The signed-in user's own token does the rest.

GET input/v1/file?path=/creators/demo_ada/&fulcra_userid=<owner id>
GET input/v1/file/<file id>/download?fulcra_userid=<owner id>
GET user/v1/dataset          # everything shared with you

2. Give one person one folder

Each creator gets their own share, so nobody sees anyone else's deal.

POST user/v1/datashare
{ "datashare_name": "Creator status",
  "fulcra_data_types": ["file:/creators/demo_ada/"],
  "share_all_data": false,
  "permissions": [{ "allowed_fulcra_userid": "<creator id>" }] }

3. Write together with change files

Each admin appends edits to /shared/creator-desk/edits.json in their own account and shares that folder with the team. A scheduled agent, running as the team account, checks every edit against a list of allowed fields, applies it, and logs it. The desk shows unmerged edits as Pending until then.

4. Gate admin pages by Fulcra user ID

The server reads the fulcradynamics.com/userid claim from the signed-in user's token and checks it against an admin list in the app's settings. The app stores no credentials of its own: every call uses the visitor's token.

Build your own

1. Install the skills: npx skills add fulcradynamics/agent-skills
2. Tell your agent what you want, for example: "Build a web app where my clients sign in with Fulcra and see the status of their project."
3. The agent plans milestones, builds and checks each one, and deploys to <name>.my.fulcra.ai.