projectious-work
- 465 skills
- 0 followers
- 2 weeks ago last updated
- ▌ Task Router 4 · projectious-work bundleRoute a task description to the right processkit skill, project-specific process override, and MCP tool in a single deterministic call — use this at the start of every processkit domain task.
- ▌ LLM Evaluation 2 · projectious-workLLM output evaluation — automated metrics, LLM-as-judge, A/B testing, regression testing. Use when measuring LLM output quality, comparing prompt or model versions, building an automated eval pipeline, setting up regression tests for prompt changes, or evaluating RAG systems and bias/safety.
- ▌ Frontend Design 2 · projectious-work bundleFrontend architecture and UI design — component hierarchies, accessibility, performance, state management. Use when designing frontend architecture, building component hierarchies, making something accessible, optimizing Core Web Vitals, or choosing a state management approach.
- ▌ Alerting Oncall 2 · projectious-workAlert design and on-call practices — severity, runbooks, SLO burn-rate alerting, escalation. Use when designing alerts, writing runbooks, reducing alert fatigue, setting up escalation policies, implementing SLO-based alerting, or improving on-call processes.
- ▌ Infographics 2 · projectious-work bundleCreates data-driven infographics and charts as accessible SVG. Use when visualizing data, choosing a chart type, generating an SVG chart or infographic, or reviewing a visualization for clarity and accuracy.
- ▌ PDF Workflow 2 · projectious-workGenerating and manipulating PDF files — from HTML, DOCX, or raw content using reportlab, weasyprint, or pypdf. Use when producing PDF reports, invoices, certificates, or when merging, splitting, or extracting text from existing PDFs.
- ▌ API Design 2 · projectious-work bundleREST API design — resource naming, HTTP methods, status codes, pagination, versioning, OpenAPI. Use when designing a new REST API, reviewing API contracts, writing OpenAPI/Swagger documentation, or choosing pagination, versioning, or error-format strategies.
- ▌ Skill Finder 6 · projectious-work bundleNavigation aid for the processkit skill catalog — maps natural-language cues and task types to the right skill. Read this when you are unsure which skill applies to the current task, when the user names a task without naming a skill, or at session start when orienting to an unfamiliar project. Always the first skill to consult; never the last.
- ▌
- ▌ Skill Finder 7 · projectious-work bundleNavigation aid for the processkit skill catalog — maps natural-language cues and task types to the right skill. Read this when you are unsure which skill applies to the current task, when the user names a task without naming a skill, or at session start when orienting to an unfamiliar project. Always the first skill to consult; never the last.
- ▌ Team Creator 4 · projectious-work bundleCompose a provider-neutral AI team by tiering accessible models on cost-efficiency, capability, latency, and governance, then mapping the 8 processkit role archetypes onto those tiers. Use when bootstrapping a new project team, rotating after a provider change, or quarterly rebalancing. Triggers: "create my AI team", "compose a team", "rebalance the team", "review the team".
- ▌ AI Fundamentals 2 · projectious-work bundleExplain and apply core ML/AI concepts — model types, training pipelines, evaluation metrics, and neural architectures.
- ▌ RAG Engineering 2 · projectious-work bundleRetrieval-Augmented Generation pipelines — ingestion, chunking, embedding, vector stores, retrieval, evaluation. Use when building a RAG pipeline, choosing chunking strategies or embedding models, debugging retrieval quality or hallucinations, evaluating an existing RAG system, or scaling/migrating vector stores.
- ▌ SEO Optimization 2 · projectious-work bundleSEO — on-page, technical, structured data, Core Web Vitals, and mobile-first indexing. Use when optimizing a website for search engines, adding meta tags or structured data, fixing Core Web Vitals, or auditing technical SEO.
- ▌ Logging Strategy 2 · projectious-work bundleStructured logging strategy — levels, correlation IDs, context propagation, PII avoidance. Use when designing a logging approach, reviewing log statements, setting up log aggregation (ELK, Loki, CloudWatch), adding correlation IDs to a distributed system, or deciding what to log and what to keep out.
- ▌ Terraform Basics 2 · projectious-workInfrastructure-as-code with Terraform/OpenTofu — resources, state, modules, plan/apply. Use when writing `.tf` files, managing cloud infrastructure with Terraform or OpenTofu, handling state and backends, or reviewing IaC code.
- ▌ XLSX Modeling 2 · projectious-workCreating Excel spreadsheets programmatically with openpyxl — worksheets, data, formulas, charts, formatting, and named ranges. Use when generating financial models, data reports, dashboards, or any structured spreadsheet from data or templates.
- ▌ Code Review 2 · projectious-workStructured code review with a checklist covering correctness, clarity, tests, security, performance, and style. Use when reviewing a PR, diff, or set of code changes before merging — including phrases like "review this", "check my changes", or "is this ready to merge".
- ▌ Refactoring 2 · projectious-work bundleSystematic refactoring with Fowler's catalog, GoF patterns, and code smell detection. Use when restructuring code without changing behavior — cleaning up smells, applying patterns, reducing duplication, or preparing a module for an upcoming feature.
- ▌ Skill Finder 8 · projectious-work bundleNavigation aid for the processkit skill catalog — maps natural-language cues and task types to the right skill. Read this when you are unsure which skill applies to the current task, when the user names a task without naming a skill, or at session start when orienting to an unfamiliar project. Always the first skill to consult; never the last.
- ▌ Devils Advocate 2 · projectious-workSystematically challenges a plan, decision, or proposal — identifying assumptions, failure modes, and stronger alternatives. Use when asked to critique a plan, stress-test an idea, find weaknesses in a proposal, or when the user says "what am I missing" or "argue against this."
- ▌ Actor Profile 3 · projectious-work bundleCreate and maintain Actor entities — humans and AI agents that participate in the project. Use when adding a new collaborator (human or agent) to the project, updating their preferences/expertise, or querying who does what.
- ▌ Id Management 4 · projectious-work bundleGenerate unique entity IDs following the project's configured format. The write-side foundation that every entity-creating skill depends on. Use whenever a new entity is being created and needs an ID, or when validating an ID format, or to inspect the project's ID configuration.
- ▌ Skill Builder 4 · projectious-work bundleAuthor a new processkit skill end-to-end — use-case interview, frontmatter, body sections, Gotchas, and trigger-phrase generation.
- ▌ Actor Profile 4 · projectious-work bundleCreate and maintain Actor entities — humans and AI agents that participate in the project. Use when adding a new collaborator (human or agent) to the project, updating their preferences/expertise, or querying who does what.
- ▌ Skill Builder 5 · projectious-work bundleAuthor a new processkit skill end-to-end — use-case interview, frontmatter, body sections, Gotchas, and trigger-phrase generation.
- ▌ Release Audit 2 · projectious-work bundleDetect-only pre-release validation sweep over the processkit content tree. Walks entity files, SKILL.md definitions, MCP server tools, and cross-references, then emits a single human-readable report with ERROR / WARN / INFO counts. Use when the user invokes `/pk-release-audit`, before tagging a release, or any time you need a comprehensive structural health check beyond what pk-doctor covers. Detect-only; never modifies any file under `context/`.
- ▌ Onboarding Guide 2 · projectious-workGenerates a structured onboarding guide for a new agent or human joining a project — covering codebase orientation, process context, first tasks, and key contacts. Use when asked to onboard someone new, write a getting-started guide, or create a "first week" plan for a project.
- ▌ Mobile App Design 2 · projectious-work bundleMobile app UX — touch targets, navigation, platform conventions, accessibility. Use when designing mobile interfaces, reviewing mobile UX, adapting web designs for mobile, or reconciling iOS and Android conventions.
- ▌ Dockerfile Review 2 · projectious-workDockerfile best practices — layer optimization, caching, security, image size. Use when writing, reviewing, or optimizing Dockerfiles, investigating bloated images, or fixing cache-busting build orders.
- ▌ Incident Response 2 · projectious-workProduction incident handling — triage, communicate, mitigate, fix, postmortem. Use when production is broken, users are affected, an outage is in progress, or a deploy has caused regressions and the priority is restoring service.
- ▌ Kubernetes Basics 2 · projectious-work bundleKubernetes cluster management — resources, networking, storage, Helm, troubleshooting. Use when writing Kubernetes manifests, running kubectl or helm, debugging pods and services, or configuring ingress, DNS, storage, or network policies.
- ▌ DOCX Authoring 2 · projectious-workCreating Word documents programmatically with python-docx — headings, styles, tables, lists, images, and sections. Use when generating DOCX reports, proposals, contracts, letters, or any structured Word document from data or templates.
- ▌ PPTX Authoring 2 · projectious-workCreating PowerPoint presentations programmatically with python-pptx — slides, layouts, text boxes, charts, tables, and images. Use when generating slide decks, briefings, reports, or presentations from data or templates.
- ▌ Git Workflow 2 · projectious-workGit workflow conventions — branch naming, conventional commits, PR descriptions, and merge strategy. Use when deciding on a branch name, writing a commit message or PR description, or choosing a merge strategy.
- ▌ Load Testing 2 · projectious-workLoad testing methodology — test types, scenario design, capacity planning, CI integration. Use when planning or running a load test, choosing a load testing tool, designing scenarios, analyzing results, setting up performance testing in CI, or estimating capacity from test data.
- ▌ SQL Patterns 2 · projectious-work bundleSQL query patterns, schema design, and optimization — joins, CTEs, window functions, indexing, and anti-patterns. Use when writing or optimizing SQL queries, designing or reviewing a relational schema, reading EXPLAIN plans, choosing indexes, or implementing pagination, deduplication, or analytical queries.
- ▌ Tdd Workflow 2 · projectious-workTest-driven development workflow — red-green-refactor, naming, doubles, when to apply. Use when writing code with TDD, practicing the red-green-refactor cycle, deciding between TDD and test-after, naming tests, choosing test doubles, or exploring property-based and mutation testing.
- ▌ Id Management 5 · projectious-work bundleGenerate unique entity IDs following the project's configured format. The write-side foundation that every entity-creating skill depends on. Use whenever a new entity is being created and needs an ID, or when validating an ID format, or to inspect the project's ID configuration.
- ▌ Skill Builder 6 · projectious-work bundleAuthor a new processkit skill end-to-end — use-case interview, frontmatter, body sections, Gotchas, and trigger-phrase generation.
- ▌ Skill Finder 9 · projectious-work bundleNavigation aid for the processkit skill catalog — maps natural-language cues and task types to the right skill. Read this when you are unsure which skill applies to the current task, when the user names a task without naming a skill, or at session start when orienting to an unfamiliar project. Always the first skill to consult; never the last.
- ▌ Skill Finder 10 · projectious-work bundleNavigation aid for the processkit skill catalog — maps natural-language cues and task types to the right skill. Read this when you are unsure which skill applies to the current task, when the user names a task without naming a skill, or at session start when orienting to an unfamiliar project. Always the first skill to consult; never the last.
- ▌ Id Management 6 · projectious-work bundleGenerate unique entity IDs following the project's configured format. The write-side foundation that every entity-creating skill depends on. Use whenever a new entity is being created and needs an ID, or when validating an ID format, or to inspect the project's ID configuration.
- ▌ Skill Reviewer 3 · projectious-work bundleAudit an existing processkit skill against the 5 Skill Killers, the Agent Skills standard, and Anthropic's troubleshooting playbook, producing a categorized findings report and draft Gotchas.
- ▌ Metrics Management 2 · projectious-work bundleManage metric specifications and observations: quantified measures the project cares about (velocity, error rates, lead time, NPS). Use when defining or recording a quantitative measure: team velocity, error rate, lead time, customer satisfaction score.
- ▌ Metrics Monitoring 2 · projectious-work bundleApplication metrics with RED/USE methods, Prometheus types, dashboards, and SLO alerting. Use when instrumenting an application with metrics, designing dashboards, setting up alerting, choosing between metric types, defining SLIs/SLOs, or applying RED, USE, or the four golden signals.
- ▌ Postmortem Writing 2 · projectious-workBlameless postmortem writing — timeline, root cause analysis, corrective actions. Use when writing an incident postmortem, conducting a post-incident review, building a postmortem template, or coaching a team toward blameless culture.
- ▌ Latex Authoring 2 · projectious-work bundleLaTeX authoring with LuaLaTeX — document classes, math, TikZ, BibLaTeX. Use when writing or editing LaTeX documents, setting up preambles, typesetting math, building TikZ diagrams, or managing bibliographies.
- ▌ Auth Patterns 2 · projectious-work bundleAuthentication and authorization patterns — OAuth2, JWT, sessions, RBAC/ABAC. Use when implementing login flows, securing APIs, managing tokens, designing permission systems, or reviewing auth code.
- ▌ Grpc Protobuf 2 · projectious-work bundleProtobuf schema design and gRPC service patterns — streaming, error handling, backward compatibility. Use when designing .proto files, implementing gRPC services or clients, choosing a streaming pattern, handling gRPC errors, or evolving a schema without breaking consumers.
- ▌ Java Patterns 2 · projectious-workModern Java 17+ — records, sealed types, pattern matching, streams, Spring Boot. Use when writing or reviewing Java 17+ code, modernizing legacy Java, or working in Spring Boot services.
- ▌ Reflex Python 2 · projectious-work bundleReflex Python web framework for full-stack apps in pure Python — components, state, routing, and deployment. Use when building Reflex apps, designing component hierarchies, managing Reflex state, or deploying a Reflex application.
- ▌ Secure Coding 2 · projectious-work bundleSecure coding practices grounded in the OWASP Top 10. Use when reviewing code for security issues, implementing input validation, hardening web applications, or adding defenses against injection, XSS, or CSRF.
- ▌ System Design 2 · projectious-work bundleSystem design methodology — requirements, capacity estimation, component design, trade-offs. Use when designing a new distributed system, evaluating an existing architecture for scalability or cost, performing back-of-envelope capacity estimation, or preparing for a system design review.
- ▌ Skill Reviewer 4 · projectious-work bundleAudit an existing processkit skill against the 5 Skill Killers, the Agent Skills standard, and Anthropic's troubleshooting playbook, producing a categorized findings report and draft Gotchas.
- ▌ Board Of Advisors 2 · projectious-workSimulates a panel of expert advisors who each evaluate a problem from their distinct perspective — surfacing blind spots and generating more diverse thinking than a single viewpoint. Use when asked to get multiple perspectives, consult experts, think through a decision from different angles, or when a problem benefits from specialist input.
- ▌ Decision Record 4 · projectious-work bundleRecord decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.
- ▌ Gate Management 2 · projectious-work bundleManage Gate entities — validation checkpoints that processes must pass (code review, security scan, tests). Use when defining or updating a checkpoint a process must pass — code review, tests green, security scan, stakeholder approval.
- ▌ Note Management 3 · projectious-work bundleCaptures, reviews, and promotes Note entities — the lightweight knowledge capture primitive in processkit. Notes are quick-capture units (thoughts, insights, questions, references) that are reviewed periodically and promoted to WorkItems, DecisionRecords, or other primitives when they ripen. Use when the user says "remember this", "note that", "I had an idea", or when running a periodic note review session.
- ▌ Owner Profiling 2 · projectious-work bundleBuild and maintain a structured personal-context portfolio for the project owner — identity, working style, goals, team, decision patterns. Includes both an interview protocol for bootstrapping and observable-signal patterns for incremental refinement. Use to bootstrap an owner profile (interview), to refine an existing profile (target one file), or to incrementally update the profile based on observed patterns from a normal session (the agent watches for signals and proposes additions when evidence accrues).
- ▌ Role Management 2 · projectious-work bundleCreate and maintain Role entities — named sets of responsibilities that actors can fill. Use when defining a new role in the project (developer, reviewer, tech-lead, release-manager) or updating an existing role's responsibilities.
- ▌ Standup Context 5 · projectious-work bundleWrites a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.
- ▌ Standup Context 6 · projectious-work bundleWrites a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.
- ▌ Status Briefing 6 · projectious-work bundleGenerates a concise status briefing from project context — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", or "what should I focus on today."
- ▌ Embedding Vectordb 2 · projectious-workVector embeddings and vector DB patterns — model choice, similarity metrics, index tuning. Use when choosing an embedding model, picking or migrating between vector databases, optimizing semantic search quality or latency, or building a hybrid (dense + sparse) retrieval pipeline.
- ▌ Prompt Engineering 2 · projectious-work bundlePrompt design patterns — few-shot, chain-of-thought, structured output, injection defense. Use when crafting or refining LLM prompts, designing system prompts for agents, requesting structured output, defending against prompt injection, building reusable prompt templates, or iterating on prompt quality.
- ▌ Distributed Tracing 2 · projectious-workDistributed tracing with OpenTelemetry — spans, context propagation, sampling. Use when instrumenting a distributed system, debugging requests that span services, setting up OpenTelemetry, choosing a sampling strategy, or understanding latency across service boundaries.
- ▌ Error Handling 2 · projectious-workError handling across languages — Result types, exceptions, retries, circuit breakers, and structured error responses. Use when designing error handling for a module or service, choosing between Result types and exceptions, building error hierarchies, implementing retries or circuit breakers, or reviewing code for missing or poor error handling.
- ▌ Go Conventions 2 · projectious-work bundleGo idioms — error wrapping, small interfaces, goroutine lifecycle, table-driven tests. Use when writing or reviewing Go code, designing package layouts, or working through concurrency, error handling, and testing decisions.
- ▌ Nosql Patterns 2 · projectious-workNoSQL patterns for document, key-value, wide-column, and graph stores. Access-pattern-driven design and consistency models. Use when choosing between NoSQL store types, designing a document or single-table model, picking a consistency level, or migrating between relational and NoSQL.
- ▌ Pixijs Gamedev 2 · projectious-work bundlePixiJS 2D rendering and game development — sprites, animation loops, interaction, and WebGL/Canvas rendering. Use when building PixiJS apps, creating 2D games, integrating sprites and animations, or implementing interactive graphics in the browser.
- ▌ Decision Record 5 · projectious-work bundleRecord decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.
- ▌ Note Management 4 · projectious-work bundleCaptures, reviews, and promotes Note entities — the lightweight knowledge capture primitive in processkit. Notes are quick-capture units (thoughts, insights, questions, references) that are reviewed periodically and promoted to WorkItems, DecisionRecords, or other primitives when they ripen. Use when the user says "remember this", "note that", "I had an idea", or when running a periodic note review session.
- ▌ Standup Context 7 · projectious-work bundleWrites a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.
- ▌ Status Briefing 7 · projectious-work bundleGenerates a concise status briefing from project context — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", or "what should I focus on today."
- ▌ Status Briefing 8 · projectious-work bundleGenerates a concise status briefing from project context — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", or "what should I focus on today."
- ▌ Decision Record 6 · projectious-work bundleRecord decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.
- ▌ Standup Context 8 · projectious-work bundleWrites a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.
- ▌ Agent Management 2 · projectious-work bundleOrchestrate multi-agent workflows with task decomposition, role assignment, handoff protocols, and per-session context budgeting.
- ▌ Context Grooming 3 · projectious-work bundleReview and prune the project context — archive completed work, summarize stale entries, and propose disabling unused skills.
- ▌ Index Management 3 · projectious-work bundleSQLite-backed index over all entity files in the project. The read-side foundation for every other MCP server. Use whenever an agent needs to look up entities by ID, kind, state, or text — instead of grepping the filesystem.
- ▌ Scope Management 2 · projectious-work bundleManage Scope entities — bounded containers grouping related work (sprint, milestone, project, quarter). Use when creating or updating a grouping boundary — sprint, milestone, quarter, project, release — that other entities will reference.
- ▌ Session Handover 4 · projectious-work bundleWrite an end-of-session handover LogEntry capturing current state, open threads, next action, and git context for session continuity.
- ▌ Session Handover 5 · projectious-work bundleWrite an end-of-session handover LogEntry capturing current state, open threads, next action, and git context for session continuity.
- ▌ Feature Engineering 2 · projectious-workFeature engineering for ML — encoding, imputation, scaling, selection, time-series features. Use when preparing data for an ML model, encoding categoricals, handling missing data, building time-series features, or selecting features from a wide table.
- ▌ Linux Administration 2 · projectious-work bundleLinux sysadmin for developers — permissions, processes, systemd, journald, cron, disks. Use when managing Linux servers, writing systemd units, querying journalctl, debugging disk or process issues, or wiring up cron and timers.
- ▌ Data Storytelling 2 · projectious-workTranslates data analysis into clear narratives and recommendations that non-technical audiences can act on. Use when presenting analysis results, writing data-driven reports, creating executive summaries from dashboards, or when data needs to be communicated as a decision rather than as numbers.
- ▌ Code Generation 2 · projectious-workCode generation patterns — template engines, AST manipulation, scaffolding, build-step generation. Use when building or extending a code generator, choosing a template engine, deciding whether to generate code or write an abstraction, adding codegen as a build step, or implementing macro/AST transformations.
- ▌ Shell Scripting 2 · projectious-work bundleBash scripting — strict mode, quoting, arg parsing, traps, shellcheck compliance. Use when writing or reviewing bash scripts, adding error handling and argument parsing, or fixing shellcheck warnings.
- ▌ SQL Style Guide 2 · projectious-workSQL style — snake_case, singular tables, named constraints, one-clause-per-line formatting. Use when writing or reviewing SQL, designing schemas, or naming tables, columns, constraints, and migrations.
- ▌ Threat Modeling 2 · projectious-workThreat modeling with STRIDE — data flow diagrams, trust boundaries, risk. Use when designing a new system, reviewing architecture for security, conducting a security review, or prioritizing security work by risk.
- ▌ Context Grooming 4 · projectious-work bundleReview and prune the project context — archive completed work, summarize stale entries, and propose disabling unused skills.
- ▌ Index Management 4 · projectious-work bundleSQLite-backed index over all entity files in the project. The read-side foundation for every other MCP server. Use whenever an agent needs to look up entities by ID, kind, state, or text — instead of grepping the filesystem.
- ▌ Session Handover 6 · projectious-work bundleWrite an end-of-session handover LogEntry capturing current state, open threads, next action, and git context for session continuity.
- ▌ Estimation Planning 2 · projectious-workSoftware estimation and planning — story points, velocity, scope negotiation, technical debt budgeting, and statistical forecasting. Use when estimating effort, planning a sprint, negotiating scope with stakeholders, budgeting for technical debt, or forecasting completion dates.
- ▌ Status Briefing 9 · projectious-work bundleGenerates a concise status briefing from project context — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", or "what should I focus on today."
- ▌ Status Briefing 10 · projectious-work bundleGenerates a concise status briefing from project context after resolving active migrations by default — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", "pk-resume", or "what should I focus on today." Info-only mode is opt-in.
- ▌ Model Recommender 4 · projectious-work bundleRecommend the right AI model for a task by scoring candidates across six dimensions (Reasoning, Engineering, Speed, Breadth, Reliability, Governance) and displaying a spider-chart profile.
- ▌ Data Visualization 2 · projectious-work bundleChart selection, color accessibility, annotation, and dashboard design. Use when creating charts, designing dashboards, choosing visualization types, improving chart readability, or reviewing data presentations for clarity.
- ▌ Dependency Audit 2 · projectious-workAudit project dependencies for vulnerabilities and outdated packages. Use when checking the security posture of dependencies, planning updates, or running a pre-release dependency review.