Techtide replit fullstack bootstrap

TechTide Replit Full-Stack Bootstrap

Bootstrap Replit projects with a clear app contract, environment variable model, test loop, deployment boundary, and migration path back into a durable repository.

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

1. Define runtime, package manager, app entrypoint, persistence layer, and public/private environment variables.
2. Generate only the smallest vertical slice that can run in Replit and prove the app loop.
3. Add a health check, smoke test, and README commands before expanding features.
4. Keep credentials in Replit secrets and record only variable names in code or docs.
5. Plan repo migration once the prototype needs CI, private deployment, custom infrastructure, or deep tests.

Output Contract

Return a concise brief with these fields:

• bootstrap prompt
• env contract
• smoke test plan
• repo migration checklist
• 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.