Skip to content

v3.3.0 — English release

Choose a tag to compare

View all tags
@byjunyoung byjunyoung released this 26 Aug 06:17
· 161 commits to main since this release
v3.3.0
5d4556e

First tagged release. Both plugins are now fully in English, and the repo carries a getting-started path and a troubleshooting section.

fig 3.3.0 · pm 0.2.0

Everything is in English now

All fourteen skill bodies (fig 13, pm 1), the script comments, the manifests and the repo tooling were translated. Two things stayed in Korean on purpose:

  • Trigger phrases in each skill's description: — they are what makes a Korean sentence route to the right skill
  • Detection patterns in draft-conventions.py and verify.py — section names are written in the team's own language, so dropping them would narrow what the probe can find

Your output language does not change with this. meta.language decides it: auto follows whatever language you are talking in, and a tag like ko pins it. English skill bodies, Korean reports.

Getting started and troubleshooting

The README now opens the install path as prerequisites → install → point it at a file → judge the first audit, and closes with eleven troubleshooting entries — every one of them a failure actually hit in use, not a guess. Among them:

  • A report that says it ran on defaults means the config is not being read at all
  • An installed plugin is pinned by version in the cache, so editing a skill changes nothing until the version is bumped
  • A 401 from Figma covers "no token", "expired" and "invalid" alike

Fixes

  • The link to conventions.example.yaml in both READMEs pointed at a path that does not exist
  • verify.py reported qa.environments.<name> as an unknown key. It is a map whose keys the user names, like files.<fileKey>, so schema membership does not apply — both are exempt now

Full documentation: README · 한국어

Assets 2
Loading