一键在 Manus 中运行任何 Skill

open-source

星标2

分支0

更新时间2026年6月23日 19:30

Open source guidelines for tangent-shell. Use when writing user-facing text, UI copy, error messages, banners, documentation, or any content visible to users.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

TangleML

TangleML/tangent-shell

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Open Source Guidelines

tangent-shell is slated to be open-sourced soon, so treat it as an open source project today: all code, UI copy, and documentation must be vendor-neutral and usable by anyone — not just Shopify employees. Writing it vendor-neutral now avoids a painful scrub later.

Do Not Include

Company-specific references: No mentions of Shopify, internal teams, internal tools, or internal infrastructure
Internal URLs: No links to internal dashboards, wikis, Slack channels, or internal services
Infrastructure assumptions: No references to specific cloud providers, internal clusters, or internal deployment targets as if they're the only option
Internal warnings or notices: No banners, alerts, or messages about internal systems, outages, or company-specific policies
Employee-specific language: No "talk to the platform team", "file a ticket in [internal tool]", or similar

What to Do Instead

Write generic, vendor-neutral copy that applies to any user
Reference configurable settings rather than hardcoded internal values (e.g., backend URL is configurable, not pointed at an internal endpoint)
Use general cloud/ML terminology (e.g., "your backend" not "the Shopify backend")
For infrastructure-specific behavior, make it configurable via environment variables or settings, not hardcoded
Error messages should guide users to general troubleshooting steps, not internal escalation paths

Examples

// Bad — Shopify-specific
"Contact the ML Platform team on #ml-platform-support for help."
"This pipeline requires access to the Shopify GCP project."
"Warning: Shopify infrastructure maintenance scheduled."

// Good — vendor-neutral
"Check your backend connection settings."
"This pipeline requires a configured backend endpoint."
"Unable to connect to the backend. Verify your settings."

When Internal Context Is Needed

If Shopify-specific configuration or documentation is needed, it belongs in:

Environment variables (configured at deployment, not in code)
External documentation (internal wikis, not in-app)
The backend (server-side configuration, not frontend hardcoding)

Never put it in the frontend source code, UI copy, or committed configuration files.

同仓库更多 Skills

同仓库

reproduce-research

TangleML/tangent-shell

Reproduce a research paper / white paper / arXiv result as a Tangle pipeline. Use when the user asks to "reproduce", "replicate", or "implement" a paper, benchmark, or arXiv link as an experiment.

2026-07-012

tangle-cli

TangleML/tangent-shell

Drive the open-source Tangle CLI (`tangle-cli`) via Bash for local pipeline/component workflows and API-backed run submission, status, logs, and artifacts. Use whenever an agent needs to validate, hydrate, submit, inspect, or debug Tangle pipelines and runs from the command line.

2026-07-012

tangle-help

TangleML/tangent-shell

Answer Tangle product, docs, and how-to questions from a local RAG over the TangleML documentation. Use for conceptual / "what is" / "how do I" lookups, not live run or execution data.

2026-07-012

tanstack-router

TangleML/tangent-shell

TanStack Router patterns for routing, navigation, search params, and layouts. Use when creating routes, navigating, or working with URL state.

2026-07-012

revealjs

TangleML/tangent-shell

Comprehensive Reveal.js reference for building HTML slide decks. Use whenever the user wants to create, revise, or extend a presentation, slide deck, or talk — especially from Markdown — including transitions, Auto-Animate, Mermaid diagrams, animatable SVG, video, backgrounds, fragments, code highlighting, speaker notes, math, themes, configuration, and PDF export.

2026-07-012

web-research

TangleML/tangent-shell

Gather, vet, and cite sources for a research question. Use when answering factual questions, comparing options, or producing an evidence-backed write-up.

2026-07-012

Open Source Guidelines

Do Not Include

Company-specific references: No mentions of Shopify, internal teams, internal tools, or internal infrastructure

Internal URLs: No links to internal dashboards, wikis, Slack channels, or internal services

Infrastructure assumptions: No references to specific cloud providers, internal clusters, or internal deployment targets as if they're the only option

Internal warnings or notices: No banners, alerts, or messages about internal systems, outages, or company-specific policies

Employee-specific language: No "talk to the platform team", "file a ticket in [internal tool]", or similar

What to Do Instead

Write generic, vendor-neutral copy that applies to any user

Reference configurable settings rather than hardcoded internal values (e.g., backend URL is configurable, not pointed at an internal endpoint)

Use general cloud/ML terminology (e.g., "your backend" not "the Shopify backend")

For infrastructure-specific behavior, make it configurable via environment variables or settings, not hardcoded

Error messages should guide users to general troubleshooting steps, not internal escalation paths

Examples

// Bad — Shopify-specific "Contact the ML Platform team on #ml-platform-support for help." "This pipeline requires access to the Shopify GCP project." "Warning: Shopify infrastructure maintenance scheduled." // Good — vendor-neutral "Check your backend connection settings." "This pipeline requires a configured backend endpoint." "Unable to connect to the backend. Verify your settings."

When Internal Context Is Needed

If Shopify-specific configuration or documentation is needed, it belongs in:

Environment variables (configured at deployment, not in code)

External documentation (internal wikis, not in-app)

The backend (server-side configuration, not frontend hardcoding)

Never put it in the frontend source code, UI copy, or committed configuration files.

name	open-source
description	Open source guidelines for tangent-shell. Use when writing user-facing text, UI copy, error messages, banners, documentation, or any content visible to users.