Techtide windows local automation guard

TechTide Windows Local Automation Guard

Run local Windows automation safely by checking resolved paths, shell boundaries, destructive command risk, background process visibility, and approval needs.

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. Resolve absolute target paths before move, delete, copy, or recursive operations.
2. Use one shell end-to-end for filesystem mutations and prefer native PowerShell cmdlets on Windows.
3. Treat background services, network listeners, and process restarts as operational changes.
4. Preview destructive actions and require explicit approval when the target is broad or ambiguous.
5. Record commands run and verification results without exposing local secrets.

Output Contract

Return a concise brief with these fields:

• command safety review
• path verification
• approval gate
• verification output
• 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.