Provides universal, remote-first patterns for list and detail page construction.

Install

mkdir -p .claude/skills/page-builder && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5672" && unzip -o skill.zip -d .claude/skills/page-builder && rm skill.zip

Installs to .claude/skills/page-builder

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Patterns for building list and detail pages with forms, filters, and data fetching
82 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Implement list pages with filtering and search
  • Build detail pages with form initialization
  • Map data types to UI components
  • Handle auto-submit filter forms
  • Manage pagination for data feeds

How it works

It uses a remote-first pattern where data fetching logic is separated from pure Svelte renderers.

Inputs & outputs

You give it
Data schema and UI requirements
You get back
Svelte page components and remote functions

When to use page-builder

  • Create a searchable list page with pagination
  • Build a detail page with an edit form
  • Map mixed data types to specific UI components

About this skill

Page Builder Patterns

Universal patterns for building pages. These apply to both public-facing and admin pages.

When to Use

  • Building list pages with filtering, search, pagination
  • Building detail/edit pages with forms
  • Rendering mixed-type feeds or lists
  • Any page that fetches and displays data

Core Principle

Remote-First: Put logic in data.remote.ts, keep pages as pure renderers.

See using-remote-functions/REMOTE-FIRST.md for the full pattern.

Page Types

TypePurposeReference
List PageDisplay items with filters/searchLIST-PAGE.md
Detail PageView/edit single item with formDETAIL-PAGE.md
Feed PageMixed-type items with componentsFEED-PAGE.md

Route Structure

src/routes/
└── [section]/
    ├── +page.svelte          # List page
    ├── data.remote.ts        # Remote functions (queries, forms)
    └── [slug]/
        └── +page.svelte      # Detail page

Key Patterns

1. Component Mapping

Map data types to components for clean rendering:

<script>
  const components = new Map([
    ['article', ArticleCard],
    ['video', VideoCard],
    ['cta', CTABanner]
  ])
</script>

{#each items as item, index (index)}
  {@const Component = components.get(item.type)}
  <Component {...item.props} />
{/each}

2. Filter Forms (Auto-Submit)

Native forms that update URL params on input:

<script>
  let form: HTMLFormElement
  function submitForm() { form.requestSubmit() }
  function debouncedSubmit() {
    clearTimeout(timer)
    timer = setTimeout(submitForm, 300)
  }
</script>

<form bind:this={form}>
  <input name="search" oninput={debouncedSubmit} />
  <select name="status" onchange={submitForm} />
</form>

3. Form Initialization

Populate forms with existing data:

<script>
  import { initForm } from '$lib/utils/form.svelte'

  initForm(updateItem, () => ({
    id: item.id,
    name: item.name ?? '',
    status: item.status ?? 'draft'
  }))
</script>

4. Pagination

<script>
  import Pagination from '$lib/ui/Pagination.svelte'
</script>

<Pagination count={totalItems} perPage={20} />

Form Components

ComponentPurpose
InputText, email, password inputs with validation
TextareaMulti-line text with validation
SelectDropdown with options
CheckboxBoolean toggle

All accept:

  • label - Field label
  • description - Helper text
  • issues - Validation errors from field.issues()
  • ...rest - Spread from field.as('type')

Remote Function Patterns

Query with Filters

const filtersSchema = z.object({
	search: z.string().catch(''),
	status: z.string().catch(''),
	page: z.number().catch(1)
})

export const getItems = query('unchecked', async (searchParams: URLSearchParams) => {
	const { locals } = getRequestEvent()
	const filters = parseSearchParams(filtersSchema, searchParams)
	return locals.service.getFiltered(filters)
})

Form with Validation

export const updateItem = form(
	z.object({
		id: z.string(),
		name: z.string().min(1, 'Required'),
		status: z.enum(['draft', 'published'])
	}),
	async (data) => {
		const { locals } = getRequestEvent()
		await locals.service.update(data.id, data)
		return { success: true }
	}
)

Reference Files

When not to use it

  • When building static pages without data fetching

Limitations

  • Requires Svelte framework
  • Dependent on remote function patterns

How it compares

It enforces a strict separation between data fetching and presentation compared to monolithic page development.

Compared to similar skills

page-builder side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
page-builder (this skill)17moNo flagsIntermediate
svelte-ui-design239moNo flagsIntermediate
worklog-design02moNo flagsAdvanced
tanstack-form162moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry