[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWAT30N317YVVFZ23PRSA2":3,"skill-same:01M6JWAT30N317YVVFZ23PRSA2":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6JWAT30N317YVVFZ23PRSA2","closure",null,"Apply the Gestalt principle of Closure — the perceptual tendency to see incomplete shapes as whole. Use when designing icons (a few strokes can imply a closed shape), illustrations (negative space defines forms), logos (the IBM stripes, the WWF panda, the FedEx arrow), card layouts (cards don't need full borders to feel like containers), or any visual that benefits from suggested rather than fully drawn shapes. Closure lets you communicate more with less; the user's perception completes the form.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fclosure\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"card","when","apply","can","more","benefits","you","with","communicate","form","containers","perception","as","full","visual","forms","shape","use","ibm","arrow","icons","2026-11-10 10:12:30",false,"---\nname: closure\ndescription: 'Apply the Gestalt principle of Closure — the perceptual tendency to see incomplete shapes as whole. Use when designing icons (a few strokes can imply a closed shape), illustrations (negative space defines forms), logos (the IBM stripes, the WWF panda, the FedEx arrow), card layouts (cards don''t need full borders to feel like containers), or any visual that benefits from suggested rather than fully drawn shapes. Closure lets you communicate more with less; the user''s perception completes the form.'\n---\n\n# Closure\n\n> **Definition.** Closure is the Gestalt principle that the visual system tends to perceive incomplete shapes as complete — to \"close\" gaps in outlines and recognize implied forms. A circle with small breaks in its outline is still seen as a circle. A few strokes that suggest a face are perceived as a face. Negative space between objects can imply a third object that isn't actually drawn. The brain fills in what isn't there.\n\nThe classic Gestalt demonstrations of closure use simple shapes with strategic gaps. A \"circle\" made of 12 dot pairs around its circumference reads as a circle, not as 24 dots. A \"triangle\" formed by three Pac-Man-shaped figures (the Kanizsa triangle) is perceived clearly even though no triangle is actually drawn — only the gaps imply one.\n\nThis perceptual tendency has substantial design value. It lets you communicate forms with less visual information than would be needed to draw them fully. The result is interfaces that feel light, illustrations that feel modern, logos that work at many sizes, and visual cues that work even at minimum scale.\n\n## Why closure matters\n\nClosure does several useful jobs in design:\n\n**Visual economy.** A form suggested by a few strokes is faster to read than a fully-rendered form, and it scales better — a partial shape can communicate at sizes where a fully detailed shape would be a blur.\n\n**Visual elegance.** Designs that exploit closure feel modern and crafted. The viewer participates in completing the form, which creates a small moment of cognitive engagement.\n\n**Memorable iconography.** Logos and icons that use closure are often more memorable than fully-drawn equivalents. The FedEx logo's hidden arrow (in the negative space between E and X) is a famous example — once you see it, you can't unsee it.\n\n**Reduced visual weight.** A card with subtle visual cues at its corners (rather than a full border) feels lighter than a card with a heavy outline. The closure principle lets the user perceive the container even though most of its border isn't drawn.\n\n## When to use closure\n\n**Icon design.** A simple icon often communicates more clearly than a detailed one. A few strokes that imply the form let the user's perception complete it.\n\n**Logo design.** Marks that exploit closure (hidden shapes in negative space, partial outlines that suggest the whole) are more memorable and often more flexible across sizes.\n\n**Card layouts.** Cards don't always need full borders. Subtle background tinting, drop shadow, or just consistent spacing can imply containment without drawing every edge.\n\n**Illustration.** Modern illustration often relies on suggested forms — silhouettes, abstracted shapes, partial details. The viewer fills in what's not shown.\n\n**Charts and diagrams.** Implied baselines, suggested axes, and visual rhythms can replace explicit lines and grids, reducing visual noise while preserving the structure.\n\n## Diagnosing closure problems\n\nWhen closure fails, the user perceives the form as broken or incomplete rather than as a whole. Symptoms:\n\n**The \"form\" doesn't read as one shape.** Users see disconnected parts rather than the implied whole. The gaps are too large or the parts too varied.\n\n**An icon's meaning is unclear.** The simplification went too far; the user can't recognize what the icon depicts.\n\n**Cards or containers feel ambiguous.** Without a clear edge cue, users aren't sure where one container ends and another begins.\n\n**Negative-space shapes go unnoticed.** A hidden shape in a logo that no one ever sees. The closure works only if the suggestion is strong enough.\n\n## Sub-skills in this cluster\n\n- **closure-implied-shapes** — Designing forms that exploit closure: icons with partial outlines, logos with negative-space shapes, illustrations with suggested rather than drawn forms.\n- **closure-completion-cost** — When closure is the wrong choice: situations where the user shouldn't have to do completion work (high-stakes interfaces, accessibility-critical contexts, novice users).\n\n## Worked examples\n\n### A minimal card layout\n\nA dashboard shows cards with content. Instead of a full border around each card, the cards have:\n- A slight elevation (subtle drop shadow).\n- Consistent internal padding.\n- A clear color change (white on a slightly darker background).\n\nThe user perceives each card as a contained unit, even though no edge is fully drawn. The closure principle does the work of containment with less visual weight than a full border would.\n\n### A logo with a hidden shape\n\nThe FedEx logo: the white space between the E and the X forms an arrow. Once you see it, you always see it. The arrow communicates speed and forward-motion without being explicitly drawn. The closure principle lets the negative space carry meaning.\n\nThe WWF panda logo similarly uses closure: the panda's body is suggested by a few black shapes; the white parts of the panda are entirely implied. Yet the form is unmistakable.\n\n### An icon that uses partial outlines\n\nA \"send\" icon often shows a paper airplane silhouette, sometimes with the back fold suggested by a single line rather than fully drawn. The user perceives the airplane through the suggested form. At small sizes, the partial drawing actually reads more clearly than a fully detailed paper airplane would.\n\n### A loading spinner that uses closure\n\nA common loading spinner: a circle with a gap that rotates. The gap implies the circle (the brain still sees a circle), and the rotation indicates progress. The minimal form is animated to convey \"working\" without filling the screen with detail.\n\n### Closure that fails: an over-simplified icon\n\nA custom icon for \"user settings\" simplifies a person + gear shape into a few abstract curves. Users can't recognize the form; the simplification went too far. The closure principle requires the user to fill in the form, but they can't fill in something they don't recognize.\n\nThe fix: include enough recognizable features (a clear human silhouette + a clear gear) that the form is identifiable, then strip the rest.\n\n### Negative-space chart structure\n\nA chart showing data over time uses a subtle baseline (a thin gray line) rather than a full axis with tick marks and gridlines. The implied structure is enough; the user reads the chart correctly without the explicit scaffolding. The chart feels lighter and more elegant.\n\n## Anti-patterns\n\n**Over-simplification.** Stripping a form down past the point of recognizability. The closure principle requires that the user can complete the form; if they can't recognize what's being suggested, they can't complete it.\n\n**Closure used where clarity is critical.** A \"delete\" icon rendered as a few abstract strokes that the user has to interpret. In high-stakes contexts, the user needs explicit forms, not suggested ones.\n\n**Closure for decoration.** A logo or icon designed to \"have a hidden shape\" that's so subtle no one notices. If the closure isn't perceived, it's just decoration that adds nothing.\n\n**Container ambiguity.** Cards without clear separation from each other or from the background. Users can't tell where one card ends and another begins. Either reduce the closure work (add more cues) or commit to fully-drawn containers.\n\n**Closure that works in one rendering and fails in another.** A form that reads correctly at large sizes and breaks down at small sizes. Test at all the sizes the form will be used.\n\n**Closure ignoring accessibility.** Forms suggested through visual cues that aren't accessible to users with vision differences. Some closure designs are inherently visual (a hidden shape in a logo); others can be supported with text alternatives.\n\n## Heuristic checklist\n\nBefore relying on closure, ask: **Does the suggested form read as a recognizable whole at the actual rendering size?** Test it. **Will the user notice the closure?** If the suggestion is too subtle, it adds nothing. **Is the user audience equipped to do the completion work?** Novices and accessibility audiences may benefit from explicit forms. **Is closure being used to communicate, or just to decorate?** Closure should do work, not just look clever.\n\n## Related principles\n\n- **Gestalt grouping principles generally** — closure is one of the original Gestalt principles.\n- **Figure-ground relationship** — closure interacts with figure-ground; what's perceived as \"figure\" tends to be the closed form.\n- **Signal-to-Noise Ratio** — closure reduces visual weight by suggesting rather than drawing.\n- **Iconic Representation** — minimal icons rely on closure to communicate.\n- **Form Follows Function** — the closure principle expresses the form's function with the minimum visual that does the job.\n\n## See also\n\n- `references\u002Flineage.md` — origins in Gestalt psychology, particularly the Kanizsa illusions.\n- `closure-implied-shapes\u002F` — sub-skill on designing forms that exploit closure.\n- `closure-completion-cost\u002F` — sub-skill on when closure is the wrong choice.\n","# Closure\n\n> **Definition.** Closure is the Gestalt principle that the visual system tends to perceive incomplete shapes as complete — to \"close\" gaps in outlines and recognize implied forms. A circle with small breaks in its outline is still seen as a circle. A few strokes that suggest a face are perceived as a face. Negative space between objects can imply a third object that isn't actually drawn. The brain fills in what isn't there.\n\nThe classic Gestalt demonstrations of closure use simple shapes with strategic gaps. A \"circle\" made of 12 dot pairs around its circumference reads as a circle, not as 24 dots. A \"triangle\" formed by three Pac-Man-shaped figures (the Kanizsa triangle) is perceived clearly even though no triangle is actually drawn — only the gaps imply one.\n\nThis perceptual tendency has substantial design value. It lets you communicate forms with less visual information than would be needed to draw them fully. The result is interfaces that feel light, illustrations that feel modern, logos that work at many sizes, and visual cues that work even at minimum scale.\n\n## Why closure matters\n\nClosure does several useful jobs in design:\n\n**Visual economy.** A form suggested by a few strokes is faster to read than a fully-rendered form, and it scales better — a partial shape can communicate at sizes where a fully detailed shape would be a blur.\n\n**Visual elegance.** Designs that exploit closure feel modern and crafted. The viewer participates in completing the form, which creates a small moment of cognitive engagement.\n\n**Memorable iconography.** Logos and icons that use closure are often more memorable than fully-drawn equivalents. The FedEx logo's hidden arrow (in the negative space between E and X) is a famous example — once you see it, you can't unsee it.\n\n**Reduced visual weight.** A card with subtle visual cues at its corners (rather than a full border) feels lighter than a card with a heavy outline. The closure principle lets the user perceive the container even though most of its border isn't drawn.\n\n## When to use closure\n\n**Icon design.** A simple icon often communicates more clearly than a detailed one. A few strokes that imply the form let the user's perception complete it.\n\n**Logo design.** Marks that exploit closure (hidden shapes in negative space, partial outlines that suggest the whole) are more memorable and often more flexible across sizes.\n\n**Card layouts.** Cards don't always need full borders. Subtle background tinting, drop shadow, or just consistent spacing can imply containment without drawing every edge.\n\n**Illustration.** Modern illustration often relies on suggested forms — silhouettes, abstracted shapes, partial details. The viewer fills in what's not shown.\n\n**Charts and diagrams.** Implied baselines, suggested axes, and visual rhythms can replace explicit lines and grids, reducing visual noise while preserving the structure.\n\n## Diagnosing closure problems\n\nWhen closure fails, the user perceives the form as broken or incomplete rather than as a whole. Symptoms:\n\n**The \"form\" doesn't read as one shape.** Users see disconnected parts rather than the implied whole. The gaps are too large or the parts too varied.\n\n**An icon's meaning is unclear.** The simplification went too far; the user can't recognize what the icon depicts.\n\n**Cards or containers feel ambiguous.** Without a clear edge cue, users aren't sure where one container ends and another begins.\n\n**Negative-space shapes go unnoticed.** A hidden shape in a logo that no one ever sees. The closure works only if the suggestion is strong enough.\n\n## Sub-skills in this cluster\n\n- **closure-implied-shapes** — Designing forms that exploit closure: icons with partial outlines, logos with negative-space shapes, illustrations with suggested rather than drawn forms.\n- **closure-completion-cost** — When closure is the wrong choice: situations where the user shouldn't have to do completion work (high-stakes interfaces, accessibility-critical contexts, novice users).\n\n## Worked examples\n\n### A minimal card layout\n\nA dashboard shows cards with content. Instead of a full border around each card, the cards have:\n- A slight elevation (subtle drop shadow).\n- Consistent internal padding.\n- A clear color change (white on a slightly darker background).\n\nThe user perceives each card as a contained unit, even though no edge is fully drawn. The closure principle does the work of containment with less visual weight than a full border would.\n\n### A logo with a hidden shape\n\nThe FedEx logo: the white space between the E and the X forms an arrow. Once you see it, you always see it. The arrow communicates speed and forward-motion without being explicitly drawn. The closure principle lets the negative space carry meaning.\n\nThe WWF panda logo similarly uses closure: the panda's body is suggested by a few black shapes; the white parts of the panda are entirely implied. Yet the form is unmistakable.\n\n### An icon that uses partial outlines\n\nA \"send\" icon often shows a paper airplane silhouette, sometimes with the back fold suggested by a single line rather than fully drawn. The user perceives the airplane through the suggested form. At small sizes, the partial drawing actually reads more clearly than a fully detailed paper airplane would.\n\n### A loading spinner that uses closure\n\nA common loading spinner: a circle with a gap that rotates. The gap implies the circle (the brain still sees a circle), and the rotation indicates progress. The minimal form is animated to convey \"working\" without filling the screen with detail.\n\n### Closure that fails: an over-simplified icon\n\nA custom icon for \"user settings\" simplifies a person + gear shape into a few abstract curves. Users can't recognize the form; the simplification went too far. The closure principle requires the user to fill in the form, but they can't fill in something they don't recognize.\n\nThe fix: include enough recognizable features (a clear human silhouette + a clear gear) that the form is identifiable, then strip the rest.\n\n### Negative-space chart structure\n\nA chart showing data over time uses a subtle baseline (a thin gray line) rather than a full axis with tick marks and gridlines. The implied structure is enough; the user reads the chart correctly without the explicit scaffolding. The chart feels lighter and more elegant.\n\n## Anti-patterns\n\n**Over-simplification.** Stripping a form down past the point of recognizability. The closure principle requires that the user can complete the form; if they can't recognize what's being suggested, they can't complete it.\n\n**Closure used where clarity is critical.** A \"delete\" icon rendered as a few abstract strokes that the user has to interpret. In high-stakes contexts, the user needs explicit forms, not suggested ones.\n\n**Closure for decoration.** A logo or icon designed to \"have a hidden shape\" that's so subtle no one notices. If the closure isn't perceived, it's just decoration that adds nothing.\n\n**Container ambiguity.** Cards without clear separation from each other or from the background. Users can't tell where one card ends and another begins. Either reduce the closure work (add more cues) or commit to fully-drawn containers.\n\n**Closure that works in one rendering and fails in another.** A form that reads correctly at large sizes and breaks down at small sizes. Test at all the sizes the form will be used.\n\n**Closure ignoring accessibility.** Forms suggested through visual cues that aren't accessible to users with vision differences. Some closure designs are inherently visual (a hidden shape in a logo); others can be supported with text alternatives.\n\n## Heuristic checklist\n\nBefore relying on closure, ask: **Does the suggested form read as a recognizable whole at the actual rendering size?** Test it. **Will the user notice the closure?** If the suggestion is too subtle, it adds nothing. **Is the user audience equipped to do the completion work?** Novices and accessibility audiences may benefit from explicit forms. **Is closure being used to communicate, or just to decorate?** Closure should do work, not just look clever.\n\n## Related principles\n\n- **Gestalt grouping principles generally** — closure is one of the original Gestalt principles.\n- **Figure-ground relationship** — closure interacts with figure-ground; what's perceived as \"figure\" tends to be the closed form.\n- **Signal-to-Noise Ratio** — closure reduces visual weight by suggesting rather than drawing.\n- **Iconic Representation** — minimal icons rely on closure to communicate.\n- **Form Follows Function** — the closure principle expresses the form's function with the minimum visual that does the job.\n\n## See also\n\n- `references\u002Flineage.md` — origins in Gestalt psychology, particularly the Kanizsa illusions.\n- `closure-implied-shapes\u002F` — sub-skill on designing forms that exploit closure.\n- `closure-completion-cost\u002F` — sub-skill on when closure is the wrong choice.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fclosure",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill closure",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill closure",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill closure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fclosure\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Flineage.md","REFERENCE","参考文档",6335,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fclosure\u002Freferences\u002Flineage.md",[76,84,91,98,123,147],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":83},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":83},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":40},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[105,106,107,108,109,110,111,112,113,114,115,20,25,116,117,118,119,120,121,122],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","done","reviewer","io","change","cli","merge","past",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":40},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[130,131,132,118,26,133,134,135,136,137,138,139,140,141,110,142,143,144,145,146],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":164,"publishedAt":40},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[153,158,161],{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":159,"categoryName":160,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":162,"categoryName":163,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000010","后端与接口",[149,165,166,167,168,169,170,143,171,111,172,173,174,175,20,176,177,178,179,180],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]