Run any Skill in Manus with one click

pt-pt-quality

Stars0

Forks0

UpdatedJune 10, 2026 at 09:52

Use when writing, translating, or reviewing Wander & Tales content in European Portuguese (pt-PT), or before publishing a pt-PT build. It guards against the two recurring native-speaker problems (the archaic "vós" register and Brazilian gerunds) plus pt-BR vocabulary, wrong clitic placement, and spelling drift, and it enforces the project rules (no-lose tone, no dashes, canon names, associational claims). Trigger on "check the Portuguese", "review pt-PT", "is this European Portuguese", "fix the Portuguese register", "before publishing Portuguese", or any task that authors or edits pt-PT prose. The add-language skill invokes this when the new locale is pt-PT.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

agigante80

agigante80/wander-and-tales

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Technical WritersArts, Design, Entertainment, Sports, and Media Occupations·SOC 27-3042

File Explorer

3 files

SKILL.md

readonly

name

pt-pt-quality

description

Keeping European Portuguese (pt-PT) correct

Wander & Tales ships European Portuguese (Portugal), never Brazilian. A native-speaker review found the whole pt-PT corpus had been authored in the archaic "vós" register with Brazilian gerunds: both wrong for Portugal, both easy for a non-native model to produce because textbooks teach them. This skill is the guard so it does not happen again, and the tool for cleaning up when it has.

The rules live in references/pt-pt-guide.md (register, the full "vós" to "vocês" conversion table, gerunds, clitics, vocabulary, spelling, and the project rules). Read it before writing or reviewing pt-PT.

When writing or translating pt-PT

Load references/pt-pt-guide.md and obey it alongside the authoring-story-content skill. The two things to get right every time:

Address the group as "vocês" with 3rd person plural verbs ("Leiam", "São", "fizeram"), a single child as "tu". Never "vós" or its 2nd person plural verbs.
Use "a + infinitivo" for ongoing actions ("está a dormir"), never the gerund ("dormindo").

When reviewing pt-PT (the "keeps an eye on it" job)

Two passes: a mechanical scan to gather candidates, then a judgment pass.

Pass 1: scan (two finders, different jobs)

Run both. They catch almost entirely different problems, so use them together.

# A. Project register, vocabulary, tone (things LanguageTool cannot see):
bash .claude/skills/pt-pt-quality/scan.sh                 # all pt-PT content
bash .claude/skills/pt-pt-quality/scan.sh worlds/<world>/stories/<story>/content/pt-PT/*.md

# B. Grammar, spelling, accents (things scan.sh cannot see), via the
#    self-hosted LanguageTool server (URL from .env: LANGUAGETOOL_URL):
.venv/bin/python -m build check-lang --root . --locale pt-PT
.venv/bin/python -m build check-lang --root . --locale pt-PT --world <world> --story <story>

scan.sh finds the archaic "vós" register, Brazilian gerunds, pt-BR vocabulary, dashes, and no-lose tone slips. check-lang finds spelling, accent, and agreement errors. Both are candidate finders, not auto-fixers; expect false positives (for example "verdes", "testes", "quando", "lindo" from the scanner, and canon names flagged as spelling by LanguageTool). The judgment pass decides.

check-lang needs the self-hosted LanguageTool server reachable at $LANGUAGETOOL_URL (see .env.example). If it is down, check-lang exits non-zero and prints the URL it tried; scan.sh still runs without it.

Pass 2: judgment and fix

For each candidate, read it in context and apply references/pt-pt-guide.md.

Never blind-replace "vós" forms. The conjugations are irregular; use the conversion table in the guide (sois to são, Lede to Leiam, fizestes to fizeram, enfrentardes to enfrentarem, and so on). Keep "vosso/vossa" and the "-vos" clitic where they read naturally with "vocês".
Preserve everything else exactly: meaning, warmth, full accents, Markdown structure (heading levels and count, ## Stop N headings as short place names, tables, italic prompt lines, bold labels), and the canon names.
Run the reviewer checklist at the end of the guide before calling a file done.

After fixing

Validate, rebuild, and commit like any content change:

.venv/bin/python -m build validate --root .   # OK
.venv/bin/python -m build lint --root .       # 0 errors
.venv/bin/python -m pytest -q                 # green
.venv/bin/python -m build rebuild --root . --out-dir kits   # FOREGROUND only

Rebuild in the foreground (never backgrounded: the Stop-hook auto-commit can race a backgrounded rebuild and commit a partial kits tree). Then rebuild the website if pt-PT prose on a page changed, and commit and push.

Scope and siblings

This skill covers pt-PT. The same shape (a register guide plus a scanner) suits the other synced locales: es-ES has its own peninsular-Spanish review history (avoid Latin-Americanisms, use vosotros) and it-IT prefers warm colloquial Italian (voi). If those grow their own guards, mirror this layout under a sibling skill.

More from this repository

same repository

authoring-story-content

agigante80/wander-and-tales

Author or revise content for the Wander & Tales children's story-kit library: story narration (simple and rich reading levels), world lore, canon registry entries, puzzles, idea banks, rules-page text, and the Guide for the Grown-Up, in British English (en-GB, canonical) and the synced locales kept in step with it (defined in build/locales.py REQUIRED_LOCALES; currently Spanish from Spain es-ES, Italian it-IT, and European Portuguese pt-PT). Use this skill whenever you write, draft, translate, or edit any kid-facing or grown-up-facing prose or YAML content for Wander & Tales (any world or story, including The Floating Isles / The Sleeping Garden and the Greek-myth world), even when the request only says "write the story", "draft the narration", "add a creature", "translate this to Spanish", or "write the grown-up guide". It encodes the no-lose, kind-and-imaginative ethos, the writing constraints (no em or en dashes), the associational (non-causal) claims rule, reading-level and peril-tone guidance, the en-GB-

2026-06-100

es-es-quality

agigante80/wander-and-tales

Use when writing, translating, or reviewing Wander & Tales content in peninsular Spanish (es-ES, Spain), or before publishing an es-ES build. It guards against the recurring problems (addressing the players as "ustedes" instead of "vosotros", voseo, and Latin-American vocabulary) plus spelling and accent drift, and it enforces the project rules (no-lose tone, no dashes, canon names, associational claims). Trigger on "check the Spanish", "review es-ES", "is this peninsular Spanish", "fix the Spanish register", "before publishing Spanish", or any task that authors or edits es-ES prose. The add-language skill invokes this when the new locale is es-ES.

2026-06-100

it-it-quality

agigante80/wander-and-tales

Use when writing, translating, or reviewing Wander & Tales content in Italian (it-IT), or before publishing an it-IT build. It guards against the recurring problems (the formal "Lei" for players instead of "voi", stiff textbook phrasing instead of warm colloquial Italian, anglicisms, and homograph accent slips like e/e or da/da) and enforces the project rules (no-lose tone, no dashes, canon names, associational claims). Trigger on "check the Italian", "review it-IT", "is this natural Italian", "fix the Italian register", "before publishing Italian", or any task that authors or edits it-IT prose. The add-language skill invokes this when the new locale is it-IT.

2026-06-100

add-language

agigante80/wander-and-tales

Use when a maintainer wants to add a whole new language (locale) to the Wander & Tales project, for example "add German", "add European Portuguese", "add pt-BR", "support French", "translate the whole project into Polish". This is the maintainer-side, project-wide counterpart to create-story (which adds one story). It wires the locale through the build code, the test fixtures, every world's content (canon, heroes, idea banks, and every story at both reading levels), the repo-wide lexicon and the shared Guide, updates the docs and skills, then validates, rebuilds every kit, and publishes. Defers all voice, register, reading-level, peril-tone, and canon-name rules to the authoring-story-content skill. Trigger on "add <language>", "add a language", "support <language>", "make the kits available in <language>".

2026-06-060

publish-story

agigante80/wander-and-tales

Use when a maintainer wants to publish a newly added or just-merged Wander & Tales story or world to the library: make sure every declared image exists (generating the missing ones with the maintainer's key), double-review the translations, build the kits, refresh the root README catalogue, confirm the PDFs render correctly, and commit. This is the maintainer-side counterpart to the create-story skill. Trigger on requests like "publish this story", "publish the kits", "a story was merged, build and publish it", "release the new world", or "rebuild and update the README".

2026-06-060

create-story

agigante80/wander-and-tales

Use when a user wants to create their own Wander & Tales story (or a new world) and build their own printable kit to play at home. Guides choosing or creating a world, choosing or writing an idea, setting the audience and challenges, authoring the content in all the project's required languages (see build/locales.py) with image prompts, optionally generating the pictures with the user's own OpenAI key (or leaving prompts to paste elsewhere), validating, and building the printable PDFs into dist/. Defers all voice, reading-level, peril-tone, and canon-name rules to the authoring-story-content skill. Sharing the story with the public library is optional and handled by the separate contribute-story skill. Trigger on requests like "create a story", "make my own adventure", "make a kit about X", "write a new story to print", or "start a new world".

2026-06-060

name

pt-pt-quality

description

Keeping European Portuguese (pt-PT) correct

When writing or translating pt-PT

Load references/pt-pt-guide.md and obey it alongside the authoring-story-content skill. The two things to get right every time:

Address the group as "vocês" with 3rd person plural verbs ("Leiam", "São", "fizeram"), a single child as "tu". Never "vós" or its 2nd person plural verbs.
Use "a + infinitivo" for ongoing actions ("está a dormir"), never the gerund ("dormindo").

When reviewing pt-PT (the "keeps an eye on it" job)

Two passes: a mechanical scan to gather candidates, then a judgment pass.

Pass 1: scan (two finders, different jobs)

Run both. They catch almost entirely different problems, so use them together.

# A. Project register, vocabulary, tone (things LanguageTool cannot see):
bash .claude/skills/pt-pt-quality/scan.sh                 # all pt-PT content
bash .claude/skills/pt-pt-quality/scan.sh worlds/<world>/stories/<story>/content/pt-PT/*.md

# B. Grammar, spelling, accents (things scan.sh cannot see), via the
#    self-hosted LanguageTool server (URL from .env: LANGUAGETOOL_URL):
.venv/bin/python -m build check-lang --root . --locale pt-PT
.venv/bin/python -m build check-lang --root . --locale pt-PT --world <world> --story <story>

Pass 2: judgment and fix

For each candidate, read it in context and apply references/pt-pt-guide.md.

Never blind-replace "vós" forms. The conjugations are irregular; use the conversion table in the guide (sois to são, Lede to Leiam, fizestes to fizeram, enfrentardes to enfrentarem, and so on). Keep "vosso/vossa" and the "-vos" clitic where they read naturally with "vocês".
Preserve everything else exactly: meaning, warmth, full accents, Markdown structure (heading levels and count, ## Stop N headings as short place names, tables, italic prompt lines, bold labels), and the canon names.
Run the reviewer checklist at the end of the guide before calling a file done.

After fixing

Validate, rebuild, and commit like any content change:

.venv/bin/python -m build validate --root .   # OK
.venv/bin/python -m build lint --root .       # 0 errors
.venv/bin/python -m pytest -q                 # green
.venv/bin/python -m build rebuild --root . --out-dir kits   # FOREGROUND only