dimcode-darwin-arm64 0.2.9-beta.0 → 0.2.9-beta.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/bin/dimcode
CHANGED
|
Binary file
|
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: artifact-static-site
|
|
3
|
+
description: Create Dim deployable static-site Artifact outputs. Use when the user asks to create, preview, smoke-test, or deploy a static website, landing page, HTML demo, browser app, or static Artifact Deployment test that must be generated under output/index.html and published by Dim.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Artifact Static Site
|
|
7
|
+
|
|
8
|
+
## Overview
|
|
9
|
+
|
|
10
|
+
Create a static artifact that Dim can discover, deploy, and expose as a public URL. Keep generation focused on the fixed Dim static artifact contract; Dim handles Cloudflare credentials, upload, and URL reporting.
|
|
11
|
+
|
|
12
|
+
Use this skill only for static browser-rendered outputs. Artifact Deployment currently supports static-site publishing only. For Node.js, Go, Python, HTTP APIs, WebSockets, server-rendered routes, Dockerfile apps, or long-running process runtimes, explain that process/container deployment is not enabled in this version and ask the user to either generate a static artifact or create the app without Dim Artifact Deployment.
|
|
13
|
+
|
|
14
|
+
## Fixed Artifact Contract
|
|
15
|
+
|
|
16
|
+
- Always treat the artifact directory as `output`.
|
|
17
|
+
- Always treat the entry file as `output/index.html`.
|
|
18
|
+
- Do not ask the user for the artifact directory or entry file.
|
|
19
|
+
- When the user asks for a deployable static site, landing page, HTML demo, browser app, smoke test, preview, or Artifact Deployment test, automatically create `output/index.html`.
|
|
20
|
+
- If extra local files are needed, put them under `output/assets/` and reference them with relative paths from `output/index.html`.
|
|
21
|
+
- Only deviate from `output/index.html` when the current user message explicitly gives a different Dim artifact path.
|
|
22
|
+
|
|
23
|
+
## Output Contract
|
|
24
|
+
|
|
25
|
+
- Put every deployable file under `output/`.
|
|
26
|
+
- Make `output/index.html` the entry point.
|
|
27
|
+
- Use relative paths for local assets, such as `assets/app.js` or `assets/styles.css`.
|
|
28
|
+
- Prefer a single `output/index.html` with inline CSS and vanilla JavaScript for smoke tests, demos, and small browser apps.
|
|
29
|
+
- For larger sites, place local assets under `output/assets/`.
|
|
30
|
+
- Avoid external CDNs, remote fonts, analytics, third-party scripts, and network-only assets unless explicitly requested.
|
|
31
|
+
- Avoid build steps for the final artifact unless the user explicitly asks for a framework project.
|
|
32
|
+
- Do not create `app/Dockerfile` for static-site tasks.
|
|
33
|
+
- Do not put Cloudflare tokens, account IDs, API keys, or deployment credentials into generated files.
|
|
34
|
+
- Do not run `wrangler`, call Cloudflare APIs, or implement deployment logic in the generated artifact.
|
|
35
|
+
|
|
36
|
+
## Smoke Test Pattern
|
|
37
|
+
|
|
38
|
+
When asked to test static Artifact Deployment, create a single self-contained `output/index.html` page that includes:
|
|
39
|
+
|
|
40
|
+
- The title `Dim Artifact Smoke Test`.
|
|
41
|
+
- The current test time rendered by JavaScript.
|
|
42
|
+
- Three feature cards for artifact packaging, deployment, and verification.
|
|
43
|
+
- A button that reveals exactly `Artifact deployment is working`.
|
|
44
|
+
- Inline CSS and native JavaScript only.
|
|
45
|
+
|
|
46
|
+
## Finish Checklist
|
|
47
|
+
|
|
48
|
+
Before responding:
|
|
49
|
+
|
|
50
|
+
- Confirm `output/index.html` exists.
|
|
51
|
+
- Confirm every deployable file is inside `output/`.
|
|
52
|
+
- Confirm the artifact can run on a static host without a build step.
|
|
53
|
+
- Confirm there are no required external CDN, remote asset, or secret dependencies unless explicitly requested.
|
|
54
|
+
- Include the Dim artifact deployment URL if Dim returns one.
|
|
55
|
+
|
|
56
|
+
## Response Pattern
|
|
57
|
+
|
|
58
|
+
Say briefly that `output/index.html` has been created and is ready for Dim Artifact Deployment. Surface the deployment URL plainly if one is available.
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
interface:
|
|
2
|
+
display_name: "Artifact Static Site"
|
|
3
|
+
short_description: "Generate Dim static artifacts at output/index.html"
|
|
4
|
+
default_prompt: "Use $artifact-static-site to create a deployable Dim static-site Artifact. Automatically write the result to output/index.html."
|
|
5
|
+
policy:
|
|
6
|
+
allow_implicit_invocation: true
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: deep-investigate
|
|
3
|
-
description: "
|
|
3
|
+
description: "Multi Agents Looping — a multi-agent deep research protocol that spawns parallel explorer agents each round, gates every round with a fresh verifier agent, loops until coverage passes, then merges findings into a structured investigation report. Use only when the user explicitly asks for a deep investigation or a formal multi-round research effort that justifies spawning and coordinating many agents."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Deep Investigate
|