[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWBXZR05MFN8M8CSWNSD9S":3,"skill-same:01M6JWBXZR05MFN8M8CSWNSD9S":76},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6JWBXZR05MFN8M8CSWNSD9S","figure-ground-relationship",null,"Apply the Gestalt principle of Figure-Ground Relationship — the perceptual separation of what's perceived as the figure (the focus, the object) from the ground (the surrounding context). Use when designing modals, overlays, focus states, hero elements, hover treatments, layered interfaces, or any context where one element should clearly stand forward against everything else. The user's perception always sorts the visual field into figure and ground; designs that reinforce the desired sorting feel clear, while designs that fight it feel confusing.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"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\u002Ffigure-ground-relationship\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"relationship","figure ground relationship","separation","when","apply","hero","layered","overlays","object","states","it","sorting","hover","perception","element","clear","as","elements","visual","focus","use","context","2026-11-10 10:12:30",false,"---\nname: figure-ground-relationship\ndescription: 'Apply the Gestalt principle of Figure-Ground Relationship — the perceptual separation of what''s perceived as the figure (the focus, the object) from the ground (the surrounding context). Use when designing modals, overlays, focus states, hero elements, hover treatments, layered interfaces, or any context where one element should clearly stand forward against everything else. The user''s perception always sorts the visual field into figure and ground; designs that reinforce the desired sorting feel clear, while designs that fight it feel confusing.'\n---\n\n# Figure-Ground Relationship\n\n> **Definition.** Figure-ground relationship is the perceptual principle that the visual field is automatically sorted into \"figure\" (the object of focus, the thing perceived as standing forward) and \"ground\" (the context, the thing perceived as receding behind). The sorting is automatic and pre-conscious; the user doesn't choose what's figure and what's ground. The designer's job is to ensure that what should be figure (the active element, the focal point, the modal content) reads as figure, and that what should be ground (the chrome, the inactive content, the background) reads as ground.\n\nThe classic illustration is the Rubin vase — a figure that can be perceived either as a vase (with the surroundings as ground) or as two faces in profile (with the vase shape as ground). The image is deliberately ambiguous; the visual system flips between the two interpretations because neither has clear primacy.\n\nIn design we usually want unambiguous primacy. The active workspace should clearly be figure; the chrome around it should clearly be ground. The modal should clearly be figure; the page underneath should clearly recede. The hovered item should clearly come forward; the rest should fade.\n\n## The cues that signal figure\n\nThe visual system uses several cues to decide what's figure and what's ground.\n\n**Definite, closed shape.** Elements with clear, complete boundaries are perceived as figure. Loose or open shapes are perceived as ground.\n\n**Apparent closeness.** Elements that appear closer (through shadow, scale, or perspective) are perceived as figure. Elements that recede are ground.\n\n**Lower position in the visual field.** Elements positioned in the lower part of the field tend to be perceived as figure (a heuristic from real-world perception, where ground is usually at the bottom).\n\n**Smaller area.** Smaller elements are typically perceived as figure against larger backgrounds, not the reverse.\n\n**Higher contrast or saturation.** Brighter, more saturated, more contrasting elements come forward. Muted, low-contrast elements recede.\n\n**Texture and detail.** More detailed elements come forward; smoother, less detailed elements recede.\n\n**Symmetry.** Symmetric shapes tend to be perceived as figure.\n\n**Overlapping (occlusion).** Elements that occlude others are perceived as in front, hence as figure.\n\nThese cues compound. A small, sharply-defined, highly-contrasting element overlaying a large, muted, smoothly-textured background is unambiguously figure.\n\n## Why figure-ground matters\n\nWhen figure-ground is clear, the user knows where to look without effort. The active task is figure; the rest is ground. Their attention naturally goes to the figure.\n\nWhen figure-ground is ambiguous, the user has to do attention work — actively deciding what to focus on. This is tiring and slow. Layouts where everything competes for visual primacy feel chaotic; layouts where nothing has primacy feel flat.\n\nWhen figure-ground is reversed (the wrong element comes forward), the user is misled about where the focus is supposed to be. They may miss the intended focal point and pay attention to something that isn't important.\n\n## Sub-skills in this cluster\n\n- **figure-ground-cues** — The specific visual cues (shadow, scale, contrast, detail) that signal figure vs. ground, and how to apply them deliberately.\n- **figure-ground-overlays-and-modals** — The most common figure-ground design problem: overlays, modals, popovers that need to clearly come forward over the underlying page.\n\n## Worked examples\n\n### A modal with clear figure-ground\n\nA modal opens over the page. The page content fades to lower opacity (becomes ground). A scrim (semi-transparent overlay) further separates the page from the modal. The modal itself has a sharp white background, a clear edge with shadow, and full saturation.\n\nThe user's perception clearly sorts: modal is figure, page is ground. Attention naturally goes to the modal. When the modal closes, the page returns to figure status.\n\n### A modal with weak figure-ground\n\nA modal opens but the page beneath isn't visually changed (no scrim, no opacity change). The modal has a subtle border but no shadow. The figure-ground separation is weak — the modal feels like another panel on the page rather than a focused overlay.\n\nUsers can be unsure where to focus. The modal's interactivity isn't visually emphasized. The figure-ground principle hasn't done its work.\n\nThe fix: add a scrim, increase the modal's elevation (more shadow), make the page beneath visibly recede.\n\n### Hover state with figure-ground\n\nWhen a user hovers over an item in a list, the item gets a slightly lifted appearance — slightly elevated shadow, slightly more saturation, slightly larger. The other items remain ground.\n\nThe hover-triggered figure-ground shift signals interactivity and gives the user feedback about where their attention is.\n\n### A dashboard where everything competes\n\nA dashboard has 8 large cards, all with similar styling, similar weight, similar prominence. The user has no clear focal point. Every card feels like figure; nothing feels like ground.\n\nThe fix: introduce visual hierarchy through figure-ground cues. Make the most important card larger or more prominent (figure). Keep supporting cards smaller and less emphasized (ground). The user's attention now has a clear target.\n\n### Active vs. inactive workspace\n\nAn app has multiple workspaces visible (a current one and recent ones). The current workspace is rendered with full saturation, sharp shapes, and prominent contrast. The recent workspaces are rendered with reduced opacity, slightly muted colors. The figure-ground separation makes the current workspace clearly active.\n\nIf both had been styled identically, users would have to read carefully to know which workspace was active. The figure-ground cue does the work.\n\n## Anti-patterns\n\n**Reversed figure-ground.** The chrome (sidebars, headers) styled more prominently than the content. Users look at the chrome instead of the content.\n\n**No figure-ground separation.** Layouts where everything has the same visual weight. Nothing feels primary; users don't know where to focus.\n\n**Modals that don't come forward enough.** Insufficient scrim, no elevation cues. The modal blurs into the page.\n\n**Overlays that come forward too aggressively.** Heavy darkening of the background, dominant overlays that feel intrusive. The figure-ground separation is too aggressive and the user feels assaulted.\n\n**Inconsistent figure-ground treatment across the product.** Modals styled differently in different places; some come forward more than others. Users can't form expectations.\n\n**Background imagery that competes with foreground.** A photo background under text where the text is hard to read because the photo is so visually rich. The figure-ground sorting is unclear.\n\n## Heuristic checklist\n\nWhen designing a layout, ask: **What should be figure (the focal point) and what should be ground (the context)?** Be explicit about the intended sorting. **Are the visual cues reinforcing the desired sorting?** Shadow, contrast, scale, saturation should align. **At a glance, can the user identify what's primary?** If they have to think about it, the figure-ground is weak. **Does the figure-ground sorting hold up when state changes?** A modal opens, a hover happens, an item gets selected — figure-ground should re-sort cleanly.\n\n## Related principles\n\n- **Gestalt grouping principles generally** — figure-ground is one of the original Gestalt principles.\n- **Hierarchy** — figure-ground is a primary mechanism for expressing hierarchy.\n- **Signal-to-Noise Ratio** — figure should have high signal; ground should have low.\n- **Color** — color choice affects figure-ground (saturated colors come forward, muted recede).\n- **Closure** — closed forms are more likely to be perceived as figure.\n- **Layering** — explicit visual layering is a tool for figure-ground design.\n\n## See also\n\n- `references\u002Flineage.md` — origins in Gestalt psychology and the Rubin vase.\n- `figure-ground-cues\u002F` — sub-skill on the specific visual cues that signal figure vs. ground.\n- `figure-ground-overlays-and-modals\u002F` — sub-skill on the most common figure-ground design problem.\n","# Figure-Ground Relationship\n\n> **Definition.** Figure-ground relationship is the perceptual principle that the visual field is automatically sorted into \"figure\" (the object of focus, the thing perceived as standing forward) and \"ground\" (the context, the thing perceived as receding behind). The sorting is automatic and pre-conscious; the user doesn't choose what's figure and what's ground. The designer's job is to ensure that what should be figure (the active element, the focal point, the modal content) reads as figure, and that what should be ground (the chrome, the inactive content, the background) reads as ground.\n\nThe classic illustration is the Rubin vase — a figure that can be perceived either as a vase (with the surroundings as ground) or as two faces in profile (with the vase shape as ground). The image is deliberately ambiguous; the visual system flips between the two interpretations because neither has clear primacy.\n\nIn design we usually want unambiguous primacy. The active workspace should clearly be figure; the chrome around it should clearly be ground. The modal should clearly be figure; the page underneath should clearly recede. The hovered item should clearly come forward; the rest should fade.\n\n## The cues that signal figure\n\nThe visual system uses several cues to decide what's figure and what's ground.\n\n**Definite, closed shape.** Elements with clear, complete boundaries are perceived as figure. Loose or open shapes are perceived as ground.\n\n**Apparent closeness.** Elements that appear closer (through shadow, scale, or perspective) are perceived as figure. Elements that recede are ground.\n\n**Lower position in the visual field.** Elements positioned in the lower part of the field tend to be perceived as figure (a heuristic from real-world perception, where ground is usually at the bottom).\n\n**Smaller area.** Smaller elements are typically perceived as figure against larger backgrounds, not the reverse.\n\n**Higher contrast or saturation.** Brighter, more saturated, more contrasting elements come forward. Muted, low-contrast elements recede.\n\n**Texture and detail.** More detailed elements come forward; smoother, less detailed elements recede.\n\n**Symmetry.** Symmetric shapes tend to be perceived as figure.\n\n**Overlapping (occlusion).** Elements that occlude others are perceived as in front, hence as figure.\n\nThese cues compound. A small, sharply-defined, highly-contrasting element overlaying a large, muted, smoothly-textured background is unambiguously figure.\n\n## Why figure-ground matters\n\nWhen figure-ground is clear, the user knows where to look without effort. The active task is figure; the rest is ground. Their attention naturally goes to the figure.\n\nWhen figure-ground is ambiguous, the user has to do attention work — actively deciding what to focus on. This is tiring and slow. Layouts where everything competes for visual primacy feel chaotic; layouts where nothing has primacy feel flat.\n\nWhen figure-ground is reversed (the wrong element comes forward), the user is misled about where the focus is supposed to be. They may miss the intended focal point and pay attention to something that isn't important.\n\n## Sub-skills in this cluster\n\n- **figure-ground-cues** — The specific visual cues (shadow, scale, contrast, detail) that signal figure vs. ground, and how to apply them deliberately.\n- **figure-ground-overlays-and-modals** — The most common figure-ground design problem: overlays, modals, popovers that need to clearly come forward over the underlying page.\n\n## Worked examples\n\n### A modal with clear figure-ground\n\nA modal opens over the page. The page content fades to lower opacity (becomes ground). A scrim (semi-transparent overlay) further separates the page from the modal. The modal itself has a sharp white background, a clear edge with shadow, and full saturation.\n\nThe user's perception clearly sorts: modal is figure, page is ground. Attention naturally goes to the modal. When the modal closes, the page returns to figure status.\n\n### A modal with weak figure-ground\n\nA modal opens but the page beneath isn't visually changed (no scrim, no opacity change). The modal has a subtle border but no shadow. The figure-ground separation is weak — the modal feels like another panel on the page rather than a focused overlay.\n\nUsers can be unsure where to focus. The modal's interactivity isn't visually emphasized. The figure-ground principle hasn't done its work.\n\nThe fix: add a scrim, increase the modal's elevation (more shadow), make the page beneath visibly recede.\n\n### Hover state with figure-ground\n\nWhen a user hovers over an item in a list, the item gets a slightly lifted appearance — slightly elevated shadow, slightly more saturation, slightly larger. The other items remain ground.\n\nThe hover-triggered figure-ground shift signals interactivity and gives the user feedback about where their attention is.\n\n### A dashboard where everything competes\n\nA dashboard has 8 large cards, all with similar styling, similar weight, similar prominence. The user has no clear focal point. Every card feels like figure; nothing feels like ground.\n\nThe fix: introduce visual hierarchy through figure-ground cues. Make the most important card larger or more prominent (figure). Keep supporting cards smaller and less emphasized (ground). The user's attention now has a clear target.\n\n### Active vs. inactive workspace\n\nAn app has multiple workspaces visible (a current one and recent ones). The current workspace is rendered with full saturation, sharp shapes, and prominent contrast. The recent workspaces are rendered with reduced opacity, slightly muted colors. The figure-ground separation makes the current workspace clearly active.\n\nIf both had been styled identically, users would have to read carefully to know which workspace was active. The figure-ground cue does the work.\n\n## Anti-patterns\n\n**Reversed figure-ground.** The chrome (sidebars, headers) styled more prominently than the content. Users look at the chrome instead of the content.\n\n**No figure-ground separation.** Layouts where everything has the same visual weight. Nothing feels primary; users don't know where to focus.\n\n**Modals that don't come forward enough.** Insufficient scrim, no elevation cues. The modal blurs into the page.\n\n**Overlays that come forward too aggressively.** Heavy darkening of the background, dominant overlays that feel intrusive. The figure-ground separation is too aggressive and the user feels assaulted.\n\n**Inconsistent figure-ground treatment across the product.** Modals styled differently in different places; some come forward more than others. Users can't form expectations.\n\n**Background imagery that competes with foreground.** A photo background under text where the text is hard to read because the photo is so visually rich. The figure-ground sorting is unclear.\n\n## Heuristic checklist\n\nWhen designing a layout, ask: **What should be figure (the focal point) and what should be ground (the context)?** Be explicit about the intended sorting. **Are the visual cues reinforcing the desired sorting?** Shadow, contrast, scale, saturation should align. **At a glance, can the user identify what's primary?** If they have to think about it, the figure-ground is weak. **Does the figure-ground sorting hold up when state changes?** A modal opens, a hover happens, an item gets selected — figure-ground should re-sort cleanly.\n\n## Related principles\n\n- **Gestalt grouping principles generally** — figure-ground is one of the original Gestalt principles.\n- **Hierarchy** — figure-ground is a primary mechanism for expressing hierarchy.\n- **Signal-to-Noise Ratio** — figure should have high signal; ground should have low.\n- **Color** — color choice affects figure-ground (saturated colors come forward, muted recede).\n- **Closure** — closed forms are more likely to be perceived as figure.\n- **Layering** — explicit visual layering is a tool for figure-ground design.\n\n## See also\n\n- `references\u002Flineage.md` — origins in Gestalt psychology and the Rubin vase.\n- `figure-ground-cues\u002F` — sub-skill on the specific visual cues that signal figure vs. ground.\n- `figure-ground-overlays-and-modals\u002F` — sub-skill on the most common figure-ground design problem.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Ffigure-ground-relationship",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill figure-ground-relationship",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill figure-ground-relationship",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill figure-ground-relationship","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Ffigure-ground-relationship\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Flineage.md","REFERENCE","参考文档",6866,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Ffigure-ground-relationship\u002Freferences\u002Flineage.md",[77,85,92,99,125,150],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":84},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":84},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":41},"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",[],[106,107,108,109,110,111,112,113,114,115,116,22,117,118,119,120,121,122,123,124],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":41},"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",[],[132,133,134,120,135,136,137,138,139,140,141,142,143,144,111,145,146,147,148,149],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":167,"publishedAt":41},"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",[156,161,164],{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":162,"categoryName":163,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":165,"categoryName":166,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000010","后端与接口",[152,168,169,170,171,172,173,146,174,112,175,176,177,178,22,179,180,181,182,183],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]