[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QPSR8GQ6YP0DA070N75SXV":3,"skill-same:01M6QPSR8GQ6YP0DA070N75SXV":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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":14,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6QPSR8GQ6YP0DA070N75SXV","sopra-steria-brand",null,"Apply Sopra Steria brand styling to a presentation, document, web page, diagram, or other artifact when the user explicitly wants Sopra Steria branding or refers to Sopra Steria brand rules, colors, typography, logo usage, or corporate visual identity. Do not use for generic design polish or unrelated branding work.","olillevik\u002Fdotfiles","olillevik","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F836761?v=4","01M6QPQM0P3JSMXH2WS5A25DNV","Ørjan Markhus Lillevik","01M6QPQM57Y8KWZ172TY1R7RA5",0,"MIT","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fsopra-steria-brand\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"sopra steria brand","brand","unrelated","generic","apply","for","usage","visual","artifact","do","document","design","use","work","Rules","page","logo","code","copilot","github copilot","2026-11-10 10:12:30",false,"---\nname: sopra-steria-brand\ndescription: Apply Sopra Steria brand styling to a presentation, document, web page, diagram, or other artifact when the user explicitly wants Sopra Steria branding or refers to Sopra Steria brand rules, colors, typography, logo usage, or corporate visual identity. Do not use for generic design polish or unrelated branding work.\nlicense: MIT\ncompatibility: Claude Code, GitHub Copilot CLI\n---\n\n# Sopra Steria Brand\n\n## What I do\n- Apply Sopra Steria colors, typography, and visual identity to the artifact the user is working on\n- Adapt the guidance to slides, documents, UI, diagrams, and similar deliverables\n- Keep the result usable when proprietary fonts or logo files are unavailable\n- Keep the branding restrained so the artifact feels clearly branded without turning into repetitive corporate wallpaper\n\n## When to use me\nUse this skill when the user explicitly wants **Sopra Steria** branding or asks for Sopra Steria brand rules to be applied. Good triggers include requests about Sopra Steria brand colors, typography, logo usage, corporate identity, visual identity, or styling a specific asset to match Sopra Steria. Do not use it for generic requests like \"make this prettier\", \"format this document\", or branding for another company.\n\n## Inputs or prerequisites\n- An artifact to style, review, or describe\n- A request that clearly points to Sopra Steria branding\n- Any delivery constraints the user gives, such as PowerPoint, Word, HTML\u002FCSS, diagram, or template work\n\n## Core brand tokens\n\n### Colors\n| Token | Hex | Typical use |\n| --- | --- | --- |\n| Sopra Steria Purple | `#4d1d82` | Primary headings, key accents |\n| Dark Purple | `#2a1449` | Deep accents, dark backgrounds |\n| Background Purple | `#ede9f2` | Light section backgrounds |\n| Background Beige | `#fdf2e5` | Alternate light backgrounds |\n| Black | `#1d1d1b` | Body text |\n| Warm Purple | `#8b1d82` | Secondary accent |\n| Orange | `#f07d00` | Highlight and call-to-action accent |\n| Red | `#cf022b` | Warning or critical emphasis |\n| Grey | `#a8a8a7` | Neutral secondary elements |\n| Light Grey | `#ededed` | Subtle backgrounds and dividers |\n\n### Typography\n- Headings: Hurme Geometric Sans 4 Bold\n- Body: Hurme Geometric Sans 3 Regular\n- Sensible fallback when brand fonts are unavailable: Tahoma, then Arial, then sans-serif\n\n## Workflow\n1. Confirm that the request is specifically about Sopra Steria branding.\n   - If the request is only generic formatting or design polish, do not force this skill.\n   - If the company or brand is ambiguous, ask instead of assuming Sopra Steria.\n\n2. Identify the artifact and translate the brand to that medium.\n    - Slides and documents: use purple-led headings, dark readable body text, restrained orange accents, and light purple or beige section backgrounds.\n    - Web\u002FUI: expose the brand colors and font stack as reusable theme tokens.\n    - Diagrams: apply the palette sparingly and keep structure readable before decorative styling.\n   - Prefer visual branding over repeated mentions of the brand name in body copy or headings unless the user explicitly wants the name to appear.\n   - By default, use the logo sparingly. One clear placement is usually better than repeating it on every page or slide.\n\n3. Handle missing brand assets honestly.\n   - Do not invent or recreate official logos.\n   - If brand fonts are unavailable, use the defined fallbacks and say so plainly.\n   - If exact logo placement or asset files matter and are not provided, ask for them.\n   - Do not add brand slogans, taglines, or campaign lines unless the user explicitly asks for them or they are clearly required by the artifact.\n\n4. Deliver the smallest useful branded result.\n   - Prefer direct edits, theme variables, style rules, or concise guidance the user can apply immediately.\n   - Keep branding faithful without over-decorating the artifact.\n   - For presentations, default to one branded opening treatment and optional subtle closing treatment rather than branding every slide aggressively.\n\n## Output expectations\n- The output clearly reflects Sopra Steria visual identity\n- Color and typography choices are concrete enough to implement\n- Assumptions about missing fonts or logos are explicit\n- Branding is applied with restraint: no unnecessary repetition of the company name, no excessive logo repetition, and no slogan unless requested\n- The skill stays focused on brand application, not generic writing or unrelated design work\n\n## Examples\n- \"Restyle this slide deck to match Sopra Steria branding.\"\n- \"Apply Sopra Steria colors and typography to this HTML page.\"\n- \"Give me a Sopra Steria-branded theme for this document template.\"\n- \"Check whether this diagram follows Sopra Steria visual identity.\"\n","# Sopra Steria Brand\n\n## What I do\n- Apply Sopra Steria colors, typography, and visual identity to the artifact the user is working on\n- Adapt the guidance to slides, documents, UI, diagrams, and similar deliverables\n- Keep the result usable when proprietary fonts or logo files are unavailable\n- Keep the branding restrained so the artifact feels clearly branded without turning into repetitive corporate wallpaper\n\n## When to use me\nUse this skill when the user explicitly wants **Sopra Steria** branding or asks for Sopra Steria brand rules to be applied. Good triggers include requests about Sopra Steria brand colors, typography, logo usage, corporate identity, visual identity, or styling a specific asset to match Sopra Steria. Do not use it for generic requests like \"make this prettier\", \"format this document\", or branding for another company.\n\n## Inputs or prerequisites\n- An artifact to style, review, or describe\n- A request that clearly points to Sopra Steria branding\n- Any delivery constraints the user gives, such as PowerPoint, Word, HTML\u002FCSS, diagram, or template work\n\n## Core brand tokens\n\n### Colors\n| Token | Hex | Typical use |\n| --- | --- | --- |\n| Sopra Steria Purple | `#4d1d82` | Primary headings, key accents |\n| Dark Purple | `#2a1449` | Deep accents, dark backgrounds |\n| Background Purple | `#ede9f2` | Light section backgrounds |\n| Background Beige | `#fdf2e5` | Alternate light backgrounds |\n| Black | `#1d1d1b` | Body text |\n| Warm Purple | `#8b1d82` | Secondary accent |\n| Orange | `#f07d00` | Highlight and call-to-action accent |\n| Red | `#cf022b` | Warning or critical emphasis |\n| Grey | `#a8a8a7` | Neutral secondary elements |\n| Light Grey | `#ededed` | Subtle backgrounds and dividers |\n\n### Typography\n- Headings: Hurme Geometric Sans 4 Bold\n- Body: Hurme Geometric Sans 3 Regular\n- Sensible fallback when brand fonts are unavailable: Tahoma, then Arial, then sans-serif\n\n## Workflow\n1. Confirm that the request is specifically about Sopra Steria branding.\n   - If the request is only generic formatting or design polish, do not force this skill.\n   - If the company or brand is ambiguous, ask instead of assuming Sopra Steria.\n\n2. Identify the artifact and translate the brand to that medium.\n    - Slides and documents: use purple-led headings, dark readable body text, restrained orange accents, and light purple or beige section backgrounds.\n    - Web\u002FUI: expose the brand colors and font stack as reusable theme tokens.\n    - Diagrams: apply the palette sparingly and keep structure readable before decorative styling.\n   - Prefer visual branding over repeated mentions of the brand name in body copy or headings unless the user explicitly wants the name to appear.\n   - By default, use the logo sparingly. One clear placement is usually better than repeating it on every page or slide.\n\n3. Handle missing brand assets honestly.\n   - Do not invent or recreate official logos.\n   - If brand fonts are unavailable, use the defined fallbacks and say so plainly.\n   - If exact logo placement or asset files matter and are not provided, ask for them.\n   - Do not add brand slogans, taglines, or campaign lines unless the user explicitly asks for them or they are clearly required by the artifact.\n\n4. Deliver the smallest useful branded result.\n   - Prefer direct edits, theme variables, style rules, or concise guidance the user can apply immediately.\n   - Keep branding faithful without over-decorating the artifact.\n   - For presentations, default to one branded opening treatment and optional subtle closing treatment rather than branding every slide aggressively.\n\n## Output expectations\n- The output clearly reflects Sopra Steria visual identity\n- Color and typography choices are concrete enough to implement\n- Assumptions about missing fonts or logos are explicit\n- Branding is applied with restraint: no unnecessary repetition of the company name, no excessive logo repetition, and no slogan unless requested\n- The skill stays focused on brand application, not generic writing or unrelated design work\n\n## Examples\n- \"Restyle this slide deck to match Sopra Steria branding.\"\n- \"Apply Sopra Steria colors and typography to this HTML page.\"\n- \"Give me a Sopra Steria-branded theme for this document template.\"\n- \"Check whether this diagram follows Sopra Steria visual identity.\"\n",{"name":5,"license":15,"description":7,"compatibility":54},"Claude Code, GitHub Copilot CLI","main","843d37d1e917e8408eef63e4f5a0a1dee063f0e7","plugins\u002Fmy-plugin\u002Fskills\u002Fsopra-steria-brand","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Folillevik","2026-11-02 03:06:57",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add olillevik\u002Fdotfiles --skill sopra-steria-brand",{"tool":67,"command":68},"bunx","bunx skills add olillevik\u002Fdotfiles --skill sopra-steria-brand",{"tool":70,"command":71},"pnpm","pnpm dlx skills add olillevik\u002Fdotfiles --skill sopra-steria-brand","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fsopra-steria-brand\u002FSKILL.md",true,[],[76,101,123,139,153,171],{"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":85,"publishedAt":49},"01M6QPSHQTE8YJZJCXYKHW1H43","skill-creator","Create, review, and improve skills in this repository for GitHub Copilot CLI and Claude Code. Use when drafting a new skill, revising an existing skill under plugins\u002Fmy-plugin\u002Fskills\u002F, tightening trigger boundaries, or making a skill leaner and more portable.","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fskill-creator\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[86,87,88,89,48,47,90,46,91,92,41,93,94,95,96,97,98,99,34,100],"skill creator","creator","review","cli","create","repository","improve","new skill","existing skill","trigger","improve skills","github copilot cli","more","my","Existing",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":49},"01M6QPS4GBQHMFZJS97CEE32HT","set-up-workflow","Set up how this repo's issues and tickets are handled. Runs setup-matt-pocock-skills, then records the spec and ticket workflow under \"Issue tracker\" in AGENTS.md. Use only when the user explicitly asks to set up the workflow.","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fset-up-workflow\u002FSKILL.md",[107],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,89,113,48,47,46,114,115,116,41,117,118,119,120,121,97,122],"workflow","SET","up","set up workflow","github","issues","how","repo","only","tracker","ticket","tickets","records","true",{"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":49},"01M6QPRZ93DHGFEF7Z9YD5GDX0","set-up-my-plugin","Copy the minimalist-engineering principles into the user-level instruction files for Claude Code and Copilot CLI.","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fset-up-my-plugin\u002FSKILL.md",[],[130,110,111,99,131,89,113,48,47,46,132,133,134,135,136,137,138,97,122,34],"plugin","set up my plugin","engineering","user","minimalist","files","copy","engineering principles","principles",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":49},"01M6QPRTW5A9XD7M27P5RHNYJ0","set-up-hooks","Set up recommended git hooks in the current repository. Strips Claude and Copilot co-author lines from commit messages, and runs the repo's tests before each commit when it has any. Use only when the user explicitly asks to set up hooks.","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fset-up-hooks\u002FSKILL.md",[],[110,111,146,147,89,113,48,148,47,46,91,149,116,41,117,150,151,97,122,152],"hooks","set up hooks","commit","messages","tests","co","author",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":49},"01M6QPRDBW1T3DTDTGSYXDF5Q5","set-up-github","Set up a GitHub repository for trunk-based development. Squash-only merges with the PR title as the commit title, head branches deleted on merge, and a pull request required for the default branch. When the repo has CI, also requires named checks to pass and the branch to be up to date before merge. Use only when the user explicitly asks to set up GitHub.","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fset-up-github\u002FSKILL.md",[],[113,110,111,160,48,47,161,162,163,164,165,166,116,117,167,168,169,170,122,34],"set up github","pr","development","pull","ci","squash","branch","default","pr title","branches","as",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":49},"01M6QPR87674ZCQHDFMCT33ATB","minimalist-engineering","Keep code minimal and avoid over-engineering.","https:\u002F\u002Fgithub.com\u002Folillevik\u002Fdotfiles\u002Fblob\u002Fmain\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fminimalist-engineering\u002FSKILL.md",[],[132,134,178,89,113,48,47,46,179,180,181,97,122],"minimalist engineering","copilot cli","minimal","keep"]