smithery/weykon

trend2work

新项目启动、趋势?

Installation

$ npx skills add smithery/weykon --skill trend2work

Also in this package

Other skills from smithery/weykon.

npx skills add smithery/weykon

Browse all from smithery/weykon

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,966 B
  • docs SUMMARY.md 84 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Trend2Work Skill (Project Bootstrap)

This skill is intentionally split into small reference modules. Load only module(s) you need.

v1 edit scope (hard limit)

For first pass, only modify:

  • .create-together/state.json - project status
  • .create-together/context.json - project context
  • .create-together/PROJECT_BRIEF.md - human-readable project brief (must be created)
  • Output JSON files:

- project-brief.json - project brief - keywords.json - keyword analysis - template-selection.json - template choice - mcp-config.json - MCP configuration

Do not:

  • Modify any files in templates/built-in/* (unless explicitly requested)
  • Touch project code (no routing, no components, no templates)
  • Enable auth/database/payment features unless explicitly requested

Dev workflow (required)

  • Before starting: If .create-together/state.json or .create-together/context.json is missing, initialize from templates:

- python3 dev/scripts/initcreatetogether_state.py

  • Before starting: Ensure mcps/env.py is available for environment loading
  • After finishing all edits:

- Clear Next.js cache if project was initialized (prevents stale assets): - macOS/Linux: rm -rf .next - Windows (PowerShell): Remove-Item -Recurse -Force .next - Windows (cmd): rmdir /s /q .next - Then run npm run build to validate project (build + lint checks) - If it fails, fix issues only within v1 allowlist unless user expands scope

Project brief normalization

Normalize user's request first:

  • references/00-project-brief.md

Execution order

  1. Project brief: references/00-project-brief.md

- Write .create-together/PROJECT_BRIEF.md (human-readable summary for non-technical stakeholders)

  1. Keyword strategy: references/01-keyword-strategy.md
  2. Template catalog: references/02-template-catalog.md
  3. Template matching: references/03-template-matching.md
  4. MCP selection: references/04-mcp-selection.md
  5. Checklist validation: references/05-checklist.md

Hard requirement (end of skill):

  • Ensure .create-together/PROJECT_BRIEF.md exists and is up-to-date by running:

- python3 dev/scripts/renderprojectbriefmd.py --out .create-together/PROJECTBRIEF.md

Bundled script

  • dev/scripts/renderprojectbriefmd.py - render .create-together/PROJECTBRIEF.md from JSON outputs
  • dev/scripts/initcreatetogether_state.py - init .create-together/state.json and .create-together/context.json from templates
  • TODO: scripts/init_project.py - project initialization automation