{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-bigdevsoon--100-days-of-code","slug":"bigdevsoon--100-days-of-code","name":"100-days-of-code","type":"agent","url":"https://bigdevsoon.me/challenges","page_url":"https://unfragile.ai/bigdevsoon--100-days-of-code","categories":["automation"],"tags":["100daysofcode","agents","ai","ai-agents","ai-workflow","claude-code","css","figma","front-end-development","frontend","git","html","js","react","responsive-web-design","tailwindcss","tutorial","vibe","vibe-coded","vibe-coding"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"pending_review","verified":false},"capabilities":[{"id":"github-bigdevsoon--100-days-of-code__cap_0","uri":"capability://automation.workflow.daily.coding.challenge.curation.and.delivery","name":"daily-coding-challenge-curation-and-delivery","description":"Delivers a structured sequence of 100 daily web development challenges with progressive difficulty, each paired with design specifications and learning objectives. The system maintains challenge state across sessions, tracks user progress through completion milestones, and surfaces the next challenge based on streak continuity. Challenges are pre-authored with HTML/CSS/JavaScript/React focus and include Figma design files as reference materials for visual accuracy.","intents":["I want a structured 100-day learning path that builds web development skills incrementally","I need daily motivation and a clear next step to work on without decision fatigue","I want to see my progress tracked across weeks to maintain accountability"],"best_for":["junior frontend/full-stack developers building consistent coding habits","career-switchers following a guided curriculum over 100 days","developers using the challenge as a daily warm-up or skill reinforcement"],"limitations":["Fixed 100-day sequence with no branching paths — all users follow the same progression regardless of skill level","No adaptive difficulty adjustment based on completion time or quality of solutions","Challenges are pre-authored, not dynamically generated — no personalization to user interests or tech stack preferences"],"requires":["Web browser with modern JavaScript support (ES6+)","Text editor or IDE for writing HTML/CSS/JavaScript","Figma account or viewer access to reference design files (optional but recommended)","Git for version control (recommended for tracking daily commits)"],"input_types":["user selection of daily challenge","user code submission or completion status"],"output_types":["challenge description with requirements","design reference (Figma link or embedded mockup)","starter code template (optional)","progress visualization (day counter, streak)"],"categories":["automation-workflow","learning-curriculum"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-bigdevsoon--100-days-of-code__cap_1","uri":"capability://code.generation.editing.ai.assisted.code.generation.from.design.specs","name":"ai-assisted-code-generation-from-design-specs","description":"Integrates Claude AI (via Claude Code / Anthropic API) to generate starter code and solutions based on Figma design specifications and challenge requirements. The system accepts design files and natural language requirements, then produces HTML/CSS/JavaScript/React code that matches the visual specification. This leverages Claude's multimodal capabilities to interpret design intent and generate semantically correct, responsive markup.","intents":["I want AI to generate boilerplate code from a Figma design so I can focus on the harder parts","I need a reference solution to compare against my implementation","I want to understand how to translate a design into responsive code"],"best_for":["developers using AI as a learning aid to understand design-to-code translation","teams using the challenge as a code generation benchmark or testing ground","developers who want to accelerate through boilerplate and focus on custom logic"],"limitations":["AI-generated code may not follow project-specific conventions or accessibility standards without explicit prompting","Generated solutions are starting points, not production-ready — require manual review and refinement","Requires valid Anthropic API key and incurs per-request costs for Claude API calls","No guarantee of consistency across multiple generations of the same challenge"],"requires":["Anthropic API key with Claude access","Figma design file URL or embedded design specification","Challenge requirements in structured format (text or JSON)","Node.js 18+ or browser environment with API proxy for client-side calls"],"input_types":["Figma design file (image or URL)","challenge description (text)","technology preference (HTML/CSS, React, Tailwind, etc.)"],"output_types":["HTML/CSS/JavaScript code","React component with JSX","Tailwind CSS utility classes","responsive design implementation"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-bigdevsoon--100-days-of-code__cap_2","uri":"capability://automation.workflow.vibe.coding.workflow.orchestration","name":"vibe-coding-workflow-orchestration","description":"Orchestrates a multi-step workflow combining design reference, AI code generation, and manual refinement into a cohesive 'vibe coding' experience. The system chains Figma design viewing, Claude code generation, local code editing, and git commit tracking into a single narrative flow. This is implemented as a workflow agent that manages state across tools and surfaces the next action based on completion status.","intents":["I want a seamless flow from design → AI generation → my edits → git commit without tool switching","I want to see my daily work captured in git history as proof of progress","I want the challenge platform to guide me through each step without manual navigation"],"best_for":["developers who value frictionless, guided workflows over self-directed learning","teams building 'vibe coding' culture with daily AI-assisted challenges","developers using git commits as accountability mechanism for the 100-day challenge"],"limitations":["Workflow assumes linear progression — no support for non-linear or exploratory coding paths","Git integration requires local setup and manual commit; no automatic commit generation","Workflow state is not persisted across sessions without external database — progress may be lost if browser cache is cleared","No offline mode — requires internet connectivity for Figma, Claude API, and challenge platform"],"requires":["Git installed locally and repository initialized","GitHub/GitLab account for remote tracking (optional but recommended)","Anthropic API key for Claude code generation","Web browser with persistent storage (localStorage or IndexedDB) for workflow state","Text editor or IDE with git integration"],"input_types":["challenge selection","user code edits","git commit messages","completion status updates"],"output_types":["workflow state (current step, progress)","git commit history","daily challenge completion record","streak counter"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-bigdevsoon--100-days-of-code__cap_3","uri":"capability://code.generation.editing.responsive.design.validation.and.feedback","name":"responsive-design-validation-and-feedback","description":"Provides visual feedback on responsive design implementation by comparing user code against design specifications across breakpoints (mobile, tablet, desktop). The system renders the user's HTML/CSS in a multi-viewport preview, highlights deviations from the Figma design, and suggests CSS adjustments. This is implemented as a client-side rendering engine with viewport simulation and visual diff capabilities.","intents":["I want to see how my code looks on different screen sizes without manual testing","I want to know if my responsive design matches the provided mockups","I want specific feedback on which CSS properties need adjustment"],"best_for":["frontend developers learning responsive design patterns","developers who want immediate visual feedback during coding","teams using the challenge as a responsive design training tool"],"limitations":["Validation is visual/heuristic-based, not pixel-perfect — minor spacing differences may not be flagged","No accessibility validation (ARIA, semantic HTML) — focuses only on visual responsive behavior","Requires user code to be syntactically valid HTML/CSS; malformed code may not render or preview correctly","Limited to CSS-based responsiveness; no support for JavaScript-driven responsive behavior validation"],"requires":["Modern web browser with CSS Grid and Flexbox support","Valid HTML/CSS code (JavaScript optional)","Figma design file or reference image for comparison"],"input_types":["HTML/CSS code (as text or file)","target breakpoints (mobile, tablet, desktop widths)","design reference image or Figma link"],"output_types":["multi-viewport preview (side-by-side renderings)","visual diff highlighting deviations","CSS suggestions for responsive fixes","pass/fail validation report"],"categories":["code-generation-editing","image-visual"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-bigdevsoon--100-days-of-code__cap_4","uri":"capability://code.generation.editing.technology.stack.flexibility.and.template.selection","name":"technology-stack-flexibility-and-template-selection","description":"Allows users to choose their preferred technology stack (vanilla HTML/CSS/JavaScript, React, Tailwind CSS, etc.) and generates starter templates and solutions accordingly. The system maintains multiple implementations of each challenge in different tech stacks and surfaces the appropriate one based on user preference. This is implemented as a template registry with stack-specific code generation pipelines.","intents":["I want to solve the challenge using React instead of vanilla JavaScript","I want to practice Tailwind CSS, not write raw CSS","I want starter code that matches my preferred tech stack"],"best_for":["developers learning multiple frontend frameworks or CSS approaches","teams standardizing on a specific tech stack and using challenges for training","developers who want to compare implementations across different technologies"],"limitations":["Not all challenges may have implementations in all tech stacks — some stacks may have incomplete coverage","Stack-specific solutions may have different complexity levels or feature sets, making direct comparison difficult","Requires knowledge of chosen tech stack to understand and modify generated code","No automatic migration or conversion between stacks — each stack has separate implementation"],"requires":["Selection of target tech stack (HTML/CSS/JS, React, Vue, Svelte, etc.)","Appropriate runtime or build tool for chosen stack (Node.js for React, etc.)","Familiarity with chosen framework or library"],"input_types":["technology stack preference (dropdown or selection)","challenge ID","optional customization parameters (CSS framework, component library)"],"output_types":["starter template in chosen stack","AI-generated solution in chosen stack","stack-specific documentation or setup instructions","package.json or build configuration"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-bigdevsoon--100-days-of-code__cap_5","uri":"capability://automation.workflow.progress.tracking.and.streak.maintenance","name":"progress-tracking-and-streak-maintenance","description":"Tracks user progress through the 100-day challenge by recording daily completion status, maintaining streak counters, and visualizing cumulative progress. The system stores completion data in browser local storage or a backend database, calculates streak metrics (current streak, longest streak, total days completed), and displays progress via visual indicators (progress bar, calendar heatmap, day counter). This is implemented as a state management layer with persistence and streak calculation logic.","intents":["I want to see how many days I've completed and my current streak","I want visual motivation through progress visualization","I want to know if I've missed any days and need to restart my streak"],"best_for":["developers using the challenge as a habit-building tool with streak motivation","teams tracking team-wide progress and celebrating milestones","individuals who respond to gamification and visual progress indicators"],"limitations":["Streak logic is binary (day completed or not) — no partial credit for incomplete challenges","Progress data is lost if browser local storage is cleared; no automatic cloud backup without user account","No grace period for missed days — streak resets immediately on a missed day","No social features for comparing streaks or leaderboards (unless explicitly implemented)"],"requires":["Browser with localStorage or IndexedDB support","Optional: user account and backend database for cross-device persistence","JavaScript enabled for progress calculation and UI updates"],"input_types":["daily challenge completion status (boolean)","completion timestamp","optional: user account ID for cloud sync"],"output_types":["current streak (number of consecutive days)","longest streak (historical maximum)","total days completed (cumulative count)","progress visualization (progress bar, calendar, percentage)","next challenge indicator"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-bigdevsoon--100-days-of-code__cap_6","uri":"capability://automation.workflow.community.solution.sharing.and.comparison","name":"community-solution-sharing-and-comparison","description":"Enables users to share their completed challenge solutions with the community and view implementations from other developers. The system collects user submissions, displays multiple solutions for each challenge (organized by tech stack or approach), and allows comparison of different implementations. This is implemented as a submission registry with filtering and sorting capabilities, potentially with voting or rating mechanisms.","intents":["I want to see how other developers solved the same challenge","I want to share my solution and get feedback from the community","I want to learn different approaches and best practices from peer solutions"],"best_for":["developers learning from peer implementations and code review","communities building collaborative learning culture around the 100-day challenge","developers seeking validation or feedback on their solutions"],"limitations":["No built-in code review or feedback mechanism — solutions are displayed without structured critique","Quality control is minimal — poor or incorrect solutions may be visible alongside high-quality ones","No moderation or spam prevention (unless explicitly implemented) — requires community or admin oversight","Privacy concerns: sharing code publicly may expose personal or proprietary patterns"],"requires":["User account or authentication for submission","Backend database or cloud storage for solution persistence","Optional: GitHub integration for automatic solution syncing"],"input_types":["user code submission (HTML/CSS/JavaScript/React)","optional: description, tech stack tag, GitHub link","optional: rating or feedback from other users"],"output_types":["solution gallery (list of implementations for a challenge)","filtered/sorted view (by tech stack, rating, recency)","side-by-side code comparison","user profile with submitted solutions"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-bigdevsoon--100-days-of-code__cap_7","uri":"capability://image.visual.figma.design.integration.and.reference.viewing","name":"figma-design-integration-and-reference-viewing","description":"Embeds Figma design files or design previews directly into the challenge interface, allowing users to reference visual specifications without leaving the platform. The system fetches design files from Figma API or displays embedded previews, supports viewport-specific design views (mobile, tablet, desktop), and may include design inspection tools (color picker, spacing measurements). This is implemented as a Figma API integration with embedded iframe or canvas rendering.","intents":["I want to see the design mockup while coding without switching to Figma","I want to inspect design details like colors, fonts, and spacing","I want to compare my implementation against the design in real-time"],"best_for":["frontend developers who need design reference during implementation","designers and developers collaborating on challenge solutions","developers learning design-to-code translation skills"],"limitations":["Requires Figma file to be shared publicly or user to have Figma access — private files cannot be embedded","Embedded previews may have performance overhead, especially for complex designs","No design editing capability — users cannot modify designs, only view them","Design inspection tools (color picker, measurements) may not be available in all embedded views"],"requires":["Figma account and publicly shared design file","Figma API key (optional, for programmatic access)","Modern web browser with iframe support","Internet connectivity for Figma asset loading"],"input_types":["Figma file URL or design ID","viewport selection (mobile, tablet, desktop)","optional: design layer or frame selection"],"output_types":["embedded Figma preview (iframe or canvas)","design metadata (colors, typography, spacing)","viewport-specific design views","design inspection tools (color picker, measurements)"],"categories":["image-visual","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"high","permissions":["Web browser with modern JavaScript support (ES6+)","Text editor or IDE for writing HTML/CSS/JavaScript","Figma account or viewer access to reference design files (optional but recommended)","Git for version control (recommended for tracking daily commits)","Anthropic API key with Claude access","Figma design file URL or embedded design specification","Challenge requirements in structured format (text or JSON)","Node.js 18+ or browser environment with API proxy for client-side calls","Git installed locally and repository initialized","GitHub/GitLab account for remote tracking (optional but recommended)"],"failure_modes":["Fixed 100-day sequence with no branching paths — all users follow the same progression regardless of skill level","No adaptive difficulty adjustment based on completion time or quality of solutions","Challenges are pre-authored, not dynamically generated — no personalization to user interests or tech stack preferences","AI-generated code may not follow project-specific conventions or accessibility standards without explicit prompting","Generated solutions are starting points, not production-ready — require manual review and refinement","Requires valid Anthropic API key and incurs per-request costs for Claude API calls","No guarantee of consistency across multiple generations of the same challenge","Workflow assumes linear progression — no support for non-linear or exploratory coding paths","Git integration requires local setup and manual commit; no automatic commit generation","Workflow state is not persisted across sessions without external database — progress may be lost if browser cache is cleared","builder identity is not verified yet","artifact is still pending review"],"rank_breakdown":{"adoption":0.17725304559352378,"quality":0.31,"ecosystem":0.6000000000000001,"match_graph":0.25,"freshness":0.35,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.1,"match_graph":0.28,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"pending_review","updated_at":"2026-05-24T12:16:21.549Z","last_scraped_at":"2026-05-03T13:59:55.151Z","last_commit":"2026-02-14T15:00:01Z"},"community":{"stars":74,"forks":15,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=bigdevsoon--100-days-of-code","compare_url":"https://unfragile.ai/compare?artifact=bigdevsoon--100-days-of-code"}},"signature":"B4GP9n/1g33Rsl5AeeZWew77MtK0MAEBAV2tbmexR8/Y0ateJrq054bi9t/VuoyjFN3QZGjYte6sqiT4GjUsDA==","signedAt":"2026-06-22T05:30:51.121Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/bigdevsoon--100-days-of-code","artifact":"https://unfragile.ai/bigdevsoon--100-days-of-code","verify":"https://unfragile.ai/api/v1/verify?slug=bigdevsoon--100-days-of-code","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}