16 skills found
ProsperCoded / guidlineThis document outlines the core context and design principles for the Fullstack Developer (Backend-focused) portfolio website. This will serve as a constant reference for all future development. Pr
johnong04 / uiUI design and frontend aesthetics standards
ypyf / RULEStandards and best practices for developing Chrome extensions
XuHanpeace / memoryThe user prefers the assistant not to commit code changes automatically without permission. (ID: 8127631) The user prefers that new pages be implemented using Redux state management and that no test p
Izumi-Koishi / Core CodingCore Coding Standards All AI-generated and human-written code must strictly adhere to these standards to ensure consistency, quality, and maintainability. 1\. Architectural Principles
arkanwolfshade / vimThis rule file outlines best practices for vim configuration, coding standards, and development workflows to ensure consistency, efficiency, and maintainability across vim-based projects. It includes recommendations for file organization, coding patterns, performance, security, testing, tooling, and common pitfalls.
GLambard / mainLocal Deep Research is an AI-powered assistant that transforms complex questions into comprehensive, cited reports by conducting iterative analysis using any LLM across diverse knowledge sources including academic databases, scientific repositories, web content, and private document collections.
robobenjie / instantYou are an expert developer who writes full-stack apps in InstantDB, Next.js, and Tailwind developer. However InstantDB is not in your training set and you are not familiar with it. Before you write
craibo / strava_sensor_refactor_planStrava Activities and Summary data integration for Home Assistant
dikkadev / jjAct as an AI assistant responsible for version control management using jujutsu vcs (`jj`) . Your mission: manage all version control operations strictly with `jj`, never interacting with the Git
fouadalabady / type-checkingThis document serves as a comprehensive guide for developers working on the OSINT Dashboard project to understand and implement proper TypeScript type checking and error handling. It's a reference for: - Troubleshooting common type errors in the codebase - Implementing proper type safety patterns - Understanding temporary workarounds for build processes - Tracking the project's roadmap toward full type safety Developers should consult this document when encountering TypeScript errors, implementing new features that require type definitions, or when addressing build failures related to type checking.
sparesparrow / 02-mcp-typescript.rulesStandards for developing Model Context Protocol (MCP) servers and clients with TypeScript
robinswood-io / metadata-standardStandardisation des Métadonnées - Saxium Objectif: Standardiser le format des métadonnées dans tous les fichiers de règles pour permettre une détection et un chargement automatiques optimaux.
HideBa / geometry_templateGeometry Template and Instance Encoding FlatCityBuf supports CityJSON's Geometry Templates for efficient representation of repeated geometries. Template Definition (in `header.fbs`) Geometr
SwiftStrike24 / CORE-PRINCIPLESCORE PRINCIPLES Follow this list of coding principles to keep in mind for my programming and SaaS and app building journey. As of late 2025, these are the gold standards. 1. DRY (Don't Repeat Yo
CraigBell / strava_sensor_refactor_planStrava Sensor Refactor Implementation Plan Overview Refactor the Strava Home Assistant integration to use single sensors per activity type instead of individual activity sensors, remove geocode
