piezas-landing

Guides editing of the static Piezas Game landing page served from public/piezas-game/.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/ebecerra-developer/ebecerra-web --skill piezas-landing-ebecerra-developer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: piezas-landing
Source: https://github.com/ebecerra-developer/ebecerra-web/tree/main/.agents/skills/piezas-landing
Command: npx skills add https://github.com/ebecerra-developer/ebecerra-web --skill piezas-landing-ebecerra-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents mistakes when editing the Piezas Game landing page, a pure static HTML/CSS site inside public/piezas-game/ that must stay isolated from the React/Vite portfolio stack and keep working with live Play Store traffic. ## Core Features & Use Cases - Scope Guardrails: Defines exactly which files may be edited (public/piezas-game/ only) and forbids React, JSX, Tailwind, or App.css changes for Piezas work. - Routing Knowledge: Documents the /piezas-game redirect and rewrite rules in vercel.json and next.config.ts, including the /.well-known/assetlinks.json deep-link file that must not be touched. - Design System Reference: Records the landing's own CSS variable palette (--bg #FAF7F2, --amber #C17B3A, --ink #2C2416) so styles are never mixed with the portfolio theme. - Use Case: When asked to update the privacy policy or add the Play Store link, the Skill tells you to edit public/piezas-game/privacidad.html or index.html directly and manually validate /piezas-game/, /piezas-game/privacidad.html, /piezas-game/terminos.html, and /.well-known/assetlinks.json afterward. ## Quick Start Use the piezas-landing skill to update the call-to-action button text on the Piezas Game landing page.

Frequently Asked Questions about piezas-landing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit the Piezas Game landing page?▼

Edit files directly inside public/piezas-game/, which contains index.html, styles.css, privacidad.html, terminos.html, and an assets folder. Never touch src/ or use React, JSX, or Tailwind for Piezas changes; the landing is pure static HTML/CSS.

How is /piezas-game routing configured in Vercel and Next.js?▼

The /piezas-game path redirects 301 to /piezas-game/, which rewrites to /piezas-game/index.html since Next.js does not serve index.html as a directory automatically. Equivalent rules live in vercel.json or next.config.ts redirects() and rewrites().

Can I use React components or Tailwind in the Piezas landing?▼

No. The landing is pure static HTML/CSS with no relationship to the React/Vite stack. Styles belong in its own styles.css using its CSS variables, never in App.css or Tailwind utilities.

What must be validated after changing the Piezas landing page?▼

Because the page receives live Play Store traffic, manually validate /piezas-game/, /piezas-game/privacidad.html, /piezas-game/terminos.html, and /.well-known/assetlinks.json after any change. The assetlinks.json file handles Android deep links and must not be modified.

Should I edit the piezas-game-landing folder in the repository root?▼

No. The root piezas-game-landing/ folder is the outdated original copy. All future edits go directly into public/piezas-game/, which is the version actually served at ebecerra.es/piezas-game/.