---
name: julilaoshi-design
description: Create and edit visual designs with Affinity or HTML, including computer-use editing, native-file saving, browser editing and export checks. Also supports user-requested Pencil workflows. Use for editable posters, visual pages and existing design-file revisions.
---

# julilaoshi-design

Produce the user's requested editable design and a verified preview. Affinity and HTML are the primary routes; Pencil is a compatibility option. Use the user's own content and visual preferences, together with ordinary design judgment. No other design skill, private library or author-specific style is required.

## Choose the route

- Existing Affinity document or requested native vector editing: read [Affinity](references/affinity.md). Check the installed application version and the tools actually available.
- Browser-based design or HTML output: read [HTML](references/html.md). A standalone page can be authored directly; the optional bundled editor is in the full repository's `web/` directory.
- Existing `.pen` file or explicit Pencil request: read [Pencil](references/pencil.md).
- Preserve a requested format. Infer the route from the request and source; ask one short question only if a missing choice materially changes the result. Never switch an existing native file to HTML without a reason agreed with the user.
- Other desktop editors require their own verified tool access and sample-file test. Do not advertise Illustrator support as tested.

## Work

1. Read the actual source. Determine the message, audience, size, output format, editable parts and protected objects from available context. Only ask for information that changes the result.
2. Build a useful first draft or apply the requested local correction. Choose hierarchy and layout for this user's content; avoid inventing facts, forcing a house style or moving approved objects.
3. Use available computer-use tools or a verified application interface. Read the current document and selection before editing. Follow current tool documentation, without requesting broader permissions just to reduce prompts.
4. Work in a recoverable copy when testing or changing file format. Keep native source files separate from previews and generated interchange files.
5. Inspect the full result and affected detail for text clipping, overlap, wrong objects, missing resources and unintended changes. Save to the actual requested path; reopen or read back when persistence is part of the task.
6. Deliver source and preview/export as requested. State what was changed, what was actually verified and any remaining limitation. A successful tool call or changed file hash alone is not visual validation.

## Scope and privacy

This public skill supplies general tool operation and delivery checks. It excludes the maintainer's personal aesthetics, philosophy, private design methods, prompt chains, evaluation criteria and reference libraries. Do not search for or import those resources to make this skill work. Use only materials authorized for the current task; do not publish them without authorization.

Do not install software, change permissions or accept agreements merely to load this skill. Affinity and Pencil are separate third-party applications. Do not bundle their binaries, licensing state or credentials.