dimcode-linux-arm64
Advanced tools
| interface: | ||
| display_name: "Artifact Static Site" | ||
| short_description: "Generate Dim static artifacts at output/index.html" | ||
| default_prompt: "Use $artifact-static-site to create a deployable Dim static-site Artifact. Automatically write the result to output/index.html." | ||
| policy: | ||
| allow_implicit_invocation: true |
| --- | ||
| name: artifact-static-site | ||
| 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. | ||
| --- | ||
| # Artifact Static Site | ||
| ## Overview | ||
| 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. | ||
| 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. | ||
| ## Fixed Artifact Contract | ||
| - Always treat the artifact directory as `output`. | ||
| - Always treat the entry file as `output/index.html`. | ||
| - Do not ask the user for the artifact directory or entry file. | ||
| - 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`. | ||
| - If extra local files are needed, put them under `output/assets/` and reference them with relative paths from `output/index.html`. | ||
| - Only deviate from `output/index.html` when the current user message explicitly gives a different Dim artifact path. | ||
| ## Output Contract | ||
| - Put every deployable file under `output/`. | ||
| - Make `output/index.html` the entry point. | ||
| - Use relative paths for local assets, such as `assets/app.js` or `assets/styles.css`. | ||
| - Prefer a single `output/index.html` with inline CSS and vanilla JavaScript for smoke tests, demos, and small browser apps. | ||
| - For larger sites, place local assets under `output/assets/`. | ||
| - Avoid external CDNs, remote fonts, analytics, third-party scripts, and network-only assets unless explicitly requested. | ||
| - Avoid build steps for the final artifact unless the user explicitly asks for a framework project. | ||
| - Do not create `app/Dockerfile` for static-site tasks. | ||
| - Do not put Cloudflare tokens, account IDs, API keys, or deployment credentials into generated files. | ||
| - Do not run `wrangler`, call Cloudflare APIs, or implement deployment logic in the generated artifact. | ||
| ## Smoke Test Pattern | ||
| When asked to test static Artifact Deployment, create a single self-contained `output/index.html` page that includes: | ||
| - The title `Dim Artifact Smoke Test`. | ||
| - The current test time rendered by JavaScript. | ||
| - Three feature cards for artifact packaging, deployment, and verification. | ||
| - A button that reveals exactly `Artifact deployment is working`. | ||
| - Inline CSS and native JavaScript only. | ||
| ## Finish Checklist | ||
| Before responding: | ||
| - Confirm `output/index.html` exists. | ||
| - Confirm every deployable file is inside `output/`. | ||
| - Confirm the artifact can run on a static host without a build step. | ||
| - Confirm there are no required external CDN, remote asset, or secret dependencies unless explicitly requested. | ||
| - Include the Dim artifact deployment URL if Dim returns one. | ||
| ## Response Pattern | ||
| 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. |
| --- | ||
| name: deep-investigate | ||
| description: "First-principles deep investigation framework. Applies to any domain — technology, market, product, strategy. Use whenever the user asks to research, investigate, analyze, compare, evaluate, or make decisions requiring deep understanding. Also trigger proactively when discussing choices or tradeoffs that need structured analysis." | ||
| 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." | ||
| --- | ||
@@ -5,0 +5,0 @@ |
+1
-1
| { | ||
| "name": "dimcode-linux-arm64", | ||
| "version": "0.2.9-beta.0", | ||
| "version": "0.2.9-beta.1", | ||
| "description": "dimcode binary for Linux ARM64", | ||
@@ -5,0 +5,0 @@ "os": [ |
Sorry, the diff of this file is not supported yet
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
164630585
0.08%397
0.51%