TechTide Context Packaging Onboarding
Package a project for agent harnesses by preparing concise context files, command maps, architecture summaries, guardrails, and local override boundaries.
Source Pattern
This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load references/source-patterns.md when you need the source anchors and extraction rationale. Load references/adapter-map.md when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.
Workflow
- Scan package, build, test, deployment, and architecture sources before writing context.
- Summarize commands, ownership boundaries, data stores, integrations, and known sharp edges.
- Separate durable project rules from local machine overrides and private secrets.
- Add tool-specific notes for Claude Code, Codex, Cursor, and Copilot only where behavior differs.
- Keep context short enough for agents to load without drowning out the user's request.
Output Contract
Return a concise brief with these fields:
- AGENTS/CLAUDE context
- command map
- risk notes
- local override stub
- verification performed or still required
- security and privacy notes
Guardrails
- Extract reusable methods, not private local content.
- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.
- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.
- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.
- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.
Harness Policy
- Use this as a native
SKILL.md for Claude Code, Codex, Gemini, and Copilot-compatible exports.
- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.
- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.
- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.
1---2name: techtide-context-packaging-onboarding3description: Package a project for agent harnesses by preparing concise context files, command maps, architecture summaries, guardrails, and local override boundaries. Use when an agent needs Alex Cinovoj / TechTide live-coding patterns, tool routing, guarded prototype-to-production workflows, or cross-harness prompt/skill adapters.4---56# TechTide Context Packaging Onboarding78Package a project for agent harnesses by preparing concise context files, command maps, architecture summaries, guardrails, and local override boundaries.910## Source Pattern1112This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load `references/source-patterns.md` when you need the source anchors and extraction rationale. Load `references/adapter-map.md` when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.1314## Workflow15161. Scan package, build, test, deployment, and architecture sources before writing context.172. Summarize commands, ownership boundaries, data stores, integrations, and known sharp edges.183. Separate durable project rules from local machine overrides and private secrets.194. Add tool-specific notes for Claude Code, Codex, Cursor, and Copilot only where behavior differs.205. Keep context short enough for agents to load without drowning out the user's request.2122## Output Contract2324Return a concise brief with these fields:2526- AGENTS/CLAUDE context27- command map28- risk notes29- local override stub30- verification performed or still required31- security and privacy notes3233## Guardrails3435- Extract reusable methods, not private local content.36- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.37- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.38- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.39- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.4041## Harness Policy4243- Use this as a native `SKILL.md` for Claude Code, Codex, Gemini, and Copilot-compatible exports.44- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.45- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.46- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.
TechTideOhio