Sergei Stepanov
Community@RickOBrian
Principal Designer (Design System)
Agent Skills by Sergei Stepanov
Showing 7 vetted skills indexed across 1 GitHub repositories.
RickOBriands-developer-guide
Builds developer guide pages for Figma components in the Souz Design System.
RickOBriands-component-migration
Migrates legacy component implementations to canonical design system components in five gated phases.
RickOBrianguide-lint
Audits and normalizes design system guide markdown files against a structural checklist.
RickOBriands-component-audit
Classifies UI components from screenshots or Figma links against a design system catalog.
RickOBriands-component-spec
Generates cross-platform design system component specifications from Figma frames, screenshots, or text descriptions.
RickOBriands-ui-review
Reviews UI components against B2C design standards and applies token-based improvement variants.
RickOBriands-component-build
Implements Product DS components from Figma for Web, iOS, and Android with semantic tokens and review pages.
Frequently Asked Questions About Sergei Stepanov
FAQPage SchemaWhat tasks can I perform with Sergei Stepanov's design system skills?▼
You can build Figma Developer Guide pages, generate cross-platform component specs for React, SwiftUI, and Compose, audit components from screenshots or Figma links, migrate legacy implementations to canonical components, lint guide markdown files, review UI quality, and build Product DS Components from Figma.
Who are these design system skills intended for?▼
They target design system teams and principal designers maintaining the Souz Design System, plus engineers implementing components on Web (React), iOS (SwiftUI), and Android (Compose). The metadata owner field explicitly designates the design-system-team as the owning group.
How are the component audit and migration skills triggered?▼
Both use strict slash commands. Auditing runs only via /audit_component with a screenshot or Figma link. Migration activates via /migrate_component with subcommands pilot, rollout, cleanup, or status, and mass refactoring requires explicit confirmation at every gate.
What component architecture and token model does ds-component-spec use?▼
It applies a four-level architecture (Item, Surface View, Structural View, Layout) and a two-level token system (core to semantic). One description, screenshot, or Figma frame produces specifications for Web (React), iOS (SwiftUI), and Android (Compose) simultaneously.
Does ds-component-build publish releases or bump versions?▼
No. It performs layout of a Product DS Component from Figma including discovery, semantic tokens, review page, metadata, and a pending changelog, but explicitly excludes release and version bump steps. Guide-lint separately applies patch-bump versioning when normalizing guide files.