npx agentspec-cli install 3e9d344a-9270-4e46-bef4-35501ae99275 --file-type windsurf-rules→ .windsurf/rules/
<!-- WINDSURF RULE CONFIGURATION File: .windsurf/rules/00-core.md Activation: Always On Description: Core project identity and SpecKit governance loop --> # Portfolio Project — Core Context <project_identity> - Repo: D4RKL0RD-J0571N/jostinlopez.github.io (Portfolio V2.5) - Stack: React 18, Vite, TailwindCSS, Framer Motion, i18next (EN + ES) - Migrating FROM: GitHub Pages TO: Vercel - Governance: SpecKit v1 — all work is spec-driven and logged - Primary agent: Claude Opus 4.6 </project_identity> <critical_known_issues> - vite.config.js has a hardcoded `base: '/jostinlopez.github.io/'` — must be removed for Vercel - No vercel.json exists — SPA direct URLs will 404 - GitHub Actions deploy workflow must be disabled once Vercel is connected - GitHub tokens must NEVER appear in src/ — only in api/ via process.env </critical_known_issues> <speckit_loop> Before touching any file, follow this sequence: 1. READ the relevant spec in specs/ 2. PLAN — update tasks/ACTIVE.md with what you're doing 3. BUILD — smallest meaningful increment 4. CHECK — self-review against .windsurf/rules/01-code-standards.md 5. LOG — append to audit/CHANGELOG.md No undocumented changes. No spec = no code. </speckit_loop> <governance_files> - AGENTS.md → role definitions and activation (@audit, @migrate, @sync, @fix) - specs/MIGRATION.md → Vercel migration tasks M-001 to M-005 - specs/GITHUB_SYNC.md → GitHub Sync tasks GS-001 to GS-005 - tasks/BACKLOG.md → full task registry with priorities and status - tasks/ACTIVE.md → current in-flight work (update as you go) - audit/CHANGELOG.md → append-only change log (update when done) - audit/DECISIONS.md → Architectural Decision Records </governance_files> <response_format> Open every response with a status tag: [AUDIT] | [IMPLEMENTING: task-id] | [BLOCKED: reason] | [REVIEW NEEDED] | [DONE: task-id] Cite specs when making decisions: (specs/MIGRATION.md § M-001) Surface trade-offs before choosing — never silently pick one path. </response_format>
Windsurf Project Rules
1. Prompt the user for a tag name and a detailed description of the release contents. 2. Ask the user if they want to increment the latest/current version number before tagging. 3. Ensure the tag includes both the version and a descriptive suffix, and is annotated with the full description.
by AgentHub Crawler
Project-Specific Rules: .windsurfrules.md
This file documents project-specific rules, exceptions, and implementation details for this repository. For organization-wide standards, see `global_rules.md`.
by AgentHub Crawler
WINDSURFRULES
1. **Context First**: Always check `System_Directory_Tree.md` and relevant `SRF` before generating code. If you cannot find context still, provide a grep or command search on the `CodeBase_Context.md` file for relevant implementations.
by AgentHub Crawler
Sign in to leave a comment.
Windsurf Rules for Portfolione Project
This project aims to develop a modern, responsive portfolio management application built on Next.js 14, leveraging the App Router, TypeScript, and shadcn/ui components. The core functionality revolves around enabling users to view and rebalance their cryptocurrency portfolios. Initially, the application will focus on **single-chain operations on Base**, utilizing 1inch Fusion Swap for efficient token exchanges. A key architectural principle is the design of highly composable and modular swap fun
by AgentHub Crawler