estrutura-paginas

Define a standard page structure for Pokémon TCG card pages.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/afonsolelis/laudo_cards --skill estrutura-paginas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estrutura-paginas
Source: https://github.com/afonsolelis/laudo_cards/tree/main/.claude/skills/estrutura-paginas
Command: npx skills add https://github.com/afonsolelis/laudo_cards --skill estrutura-paginas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Esta Skill define uma estrutura padrão para páginas individuais de cartas Pokémon TCG graduadas, garantindo consistência e qualidade em todo o portfólio.

Core Features & Use Cases

  • Estrutura padrão completa: Navbar, Header, Conteúdo principal com seções de Fotos/Identificação, Graduação, Análise de Condição, Histórico, Observação (opcional) e Botões de navegação.
  • Guia de implementação: orienta como aplicar o layout ao criar novas cartas e revisar páginas existentes.
  • Compatibilidade com templates existentes: funciona em conjunto com pericia-template para criar perícias completas mantendo o padrão.

Quick Start

  • Ao iniciar uma nova página de carta, aplique a estrutura apresentada.
  • Combine com a perícia gerada pela skill pericia-template para preencher dados específicos.
  • Salve o resultado em pages/[nome-carta].html e inclua o link no index.html.

Frequently Asked Questions about estrutura-paginas

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

FAQPage Schema
How do I create a consistent page layout for Pokémon TCG card portfolios?

Create a standard page structure that includes Navbar, Header, Content sections (Photos/Identification, Grading, Condition Analysis, History, Notes), navigation buttons, and ensures responsive design and accessibility compliance across all card pages.

What sections should I include when designing individual Pokémon card pages?

Include a Navbar for navigation, Header for card identity, main Content with Photos/Identification and Grading sections, Condition Analysis, Historical data, optional Notes, and navigation buttons; add modals and scripts for interactivity while maintaining accessibility standards.

Can I use this page structure template with other design tools in my workflow?

Yes, this structure works alongside pericia-template to populate specific card data while maintaining layout standards. Combine both to generate complete, consistently formatted card pages saved as HTML files linked in your index.

What's the best way to ensure all Pokémon card pages follow the same design standard?

Apply this standard page structure as a template when creating new card pages and when reviewing existing layouts. It enforces consistent Navbar, Header, Content organization, modals, scripts, and responsive design requirements across your entire portfolio.

Do I need to manually code each card page or can I template the structure?

Use the provided standard structure as a template for new pages; combine it with pericia-template to automatically populate card-specific data, then save to pages/[card-name].html and link in index.html for efficiency and consistency.